UML

2012-02-26 Thread yac
Hi, im trying to use dia for UML modeling but I keep running into some
issues I hope someone can comment on.

1, http://old.nabble.com/UML2-plugin-td10290465.html any update on this?

2, Are the packages fundamentaly broken? It's major pain when moving
things around as once they are created inside or outside the package I
have to delete them and create again when i realize i want them on the
other side.

3, event source/sink attaching logic seems reversed as it is possible to
connect only an event sink to event source.


pgpIJVwurNKwQ.pgp
Description: PGP signature
___
dia-list mailing list
dia-list@gnome.org
http://mail.gnome.org/mailman/listinfo/dia-list
FAQ at http://live.gnome.org/Dia/Faq
Main page at http://live.gnome.org/Dia



organization, workflow

2012-04-12 Thread yac
Hello fellow DIA-ers,

I'm running into some issues on managing my diagrams and creating a
comfortable workflow.
-   How do You do it?

Here is my context:

Project Complexity and organization
===

I'm working on project which has subprojects
*   HW part (stationary terminals)
*   SW master server (db, web access for management)
*   SW terminal part (comunicates with the HW and master server, has
it's own db)

The project is in early stage of planning, where we design actually 2
projects.
*   1st is our idea of how it should look like "done right" and generic
*   2nd is minimal viable product we can sell to our first client, so
it has stripped down some use cases.

So my .dia files are structured on FS by the projects they belong to.

generic/uml.dia
*   belongs to main project.
*   describes logic of stuff that is relevant to every subproject.
Like state diagrams of removable HW parts attached on the
terminal. Component overview, etc.

generic/terminal/use_cases.dia
*   Use Cases for the generic project.

client/terminal/use_cases.dia
*   Use cases for the client we agreed on.

client/terminal/db.dia
client/master/db.dia

etc.

I'm not using this much DIA for long, so im continualy improving on the
workflow, but it doesnt feel really smooth like I work with source
files and git. I use Xmonad as wm, so I dont see window titles. My
windows layout looks like

++
| main big window with diagram space| second related |
|   | diagram file   |
|   ||
|   | layers |
|   ||
|   | toolbar|
++

and i'm generaly happy with it. Only I orientate which window is which
by looking at the layers window and examining the layers or Diagram:
. But this is kind of confusing since the identical names
eg. for use_cases. When I need open more diagrams I just open another
dia on another workspace.

Im realizing now I havent structured everything properly in the
filesystem, so this issue may go away once I get a grip and mindset on
this structure (this is my first project this big that needs to design
carefully and Im managing/designing by myself) but anyway ...

... here are first Qs:
*   How do you organize diagrams in such a project?
*   What do i do ineffectively / How would you go about improving this
workflow?
*   How do I orientate in the files? Would enabling window title bars
help, is there other way? or will this go away once I get the grip?
*   Is it possible to have nested layers?

Backups and sharing

Currently when I modify a file I just upload it to corresponding
redmine project to documents. Which is backed up and allows me to see
history as i upload new versions. The issue is when I get to something
after a few days i'm not sure if I uploaded or not, which checking for
is tedious. However, this can be solved just by getting discipline in
uploading at the end of every session but I'd rather not to just
because and also it happens I need to leave quickly or just added one
or two elements because I got a good idea at 2 AM.

I tried storing the files ungzipped in git for like a week but it's a
mess and grows quickly and diffs arent very helpfull. Storing them just
in binary would also grow quickly on frequent commits.

So, Qs:
*   How do you manage versioning, backuping and sharing?
*   Did you actually try using git for longer time? with what results?
___
dia-list mailing list
dia-list@gnome.org
http://mail.gnome.org/mailman/listinfo/dia-list
FAQ at http://live.gnome.org/Dia/Faq
Main page at http://live.gnome.org/Dia



Re: dia-list Digest, Vol 96, Issue 11

2012-04-17 Thread yac
On Sat, 14 Apr 2012 12:00:02 +
dia-list-requ...@gnome.org wrote:

>  Message: 2
>  Date: Fri, 13 Apr 2012 20:12:13 +0200
>  From: Steffen Macke 
>  To: discussions about usage and development of dia
>   
>  Subject: Re: organization, workflow
>  Message-ID: <4f886c7d.8090...@diagramr.biz>
>  Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>  Hi yac,
>
>  Am 04/12/2012 08:50 PM, schrieb yac:
>  > *   How do you organize diagrams in such a project?
>  I think you're in the best position to organize this. You're doing
> the work and you should feel comfortable with it.
>  > *   How do I orientate in the files? Would enabling window title
>  > bars help, is there other way? or will this go away once I get the
>  > grip?
>  I've never working without window title bars. Is your screen so small
>  that you have to get rid of them?
>  If that's the case: How about getting a bigger/additional screen?
I have big screens but still it's a feature, i generaly dont need
those, so I dont have them.

>  > *   Is it possible to have nested layers?
>  What's your problem with "just" having layers? Do you use the
> "Search" function already? In
>  complex contexts, I often prefer search over navigational structures
>  (like layers or file system trees)
I'm not a big fan of search, I know my fs, my files and my workflow.
Search for me is more like a backup solution which only have a chance
of finding what I want. But do you mean a FS search or something else?

>  > I tried storing the files ungzipped in git for like a week but
>  > it's a mess and grows quickly and diffs arent very helpfull.
>  > Storing them just in binary would also grow quickly on frequent
>  > commits.
>  What's your current data size and weekly growth? What's the disk
> space you have available?
>  Unless you're exceeding your available disk space within your project
>  period (or the next time you're
>  going to upgrade your hardware), there's no need to worry (add a
> little bit of safety margin, if you want to be on the safe side...)
>  I've successfully storedgigabytes of binary data in subversion
> (which is basically the same as git) without any problems. And that
> was several years ago.
I dont like it in principle. Currently its pretty small, like 150KB per
file but it would easily grow into tens of megabytes just after a few
days of work and then cloning would be a pain. Also it there wouldnt be
any help with merging, or does someone know of a simple method to
successfuly do merges on the dia xml? So I would get only automatic
check that stable/repo doesnt have any newer version than I have, which
could be also solved by a little caution when working with redmine
(also i dont think there would be conflict often) while I would also
get big git clones and having to teach other people to use git.

>  > *   How do you manage versioning, backuping and sharing?
>  s. above I would go for git. If there's a problem, could you
> describe it in detail?
>  > *   Did you actually try using git for longer time? with what
>  > results?
>  What's your point here? Are you worried about git's reliability? You
>  shouldn't.
>  But of course, git is NOT a substitute for backups.
>  In case you're replicating your git repository frequently to several
>  machines and you ignore that risk
>  that all these machines are compromised at the same time (e.g. by an
>  attacker or virus), a weekly backup could be sufficient. But of
> course, if your time frame is very tight and you have to avoid the
> risk of a one week data loss at all cost, you'll need more frequent
> backups...
Actually it can be. Like in environment of linux kernel, Torvalds
mentioned that he doesnt do backups anymore, it is sufficient to know
sha hash of his last commit and he can safely pull them from someone
else.

>
>  Regards,
>
>  Steffen

I think I could wrote the post in a summary like ... Have you figured
some workflow tricks that come with experience with dia?

Regards,
yac

-- 
"Ubuntu", an african word meaning, "Gentoo is too hard for me"
___
dia-list mailing list
dia-list@gnome.org
http://mail.gnome.org/mailman/listinfo/dia-list
FAQ at http://live.gnome.org/Dia/Faq
Main page at http://live.gnome.org/Dia