wiremaster-general Mailing List for WireMaster

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

http://www.4073.at/dhsiewba/rqsacfajxhpmsw=iswgmmfkglarpmike rein

Greetings,

A new Wiremaster v0.46 release candidate is ready for testing (RC4):
http://dreamingbits.com/wiremaster/WireMaster_0.46_installer_windows.exe

Here's the list of things that have changed from RC 3:
* fixed several bugs relating to multi select, via the mouse and ctrl usages
* cleaned up drag panel a bit 
* several bug fixes resulting from QA on RC 3.

Any help you can give in testing this release would be very much appreciated.

Jeff, do you think you'll have some time to help write release notes and a news blurb for the upcoming release? Doesn't have to be really long, basically just a recap of what's in the new release.

Thanks!

-Mike

Hey again,

A new Wiremaster v0.46 release candidate is ready for testing (RC3):
http://dreamingbits.com/wiremaster/WireMaster_0.46_installer_windows.exe

Here's the list of things that have changed from RC 2:
* fixed issue when dragging multiple components (regression bug, not in tracker)
* fixed mouse based multi selection to work when dragging torwards west or north
* added missing reference to label for each annotation in wireframe html output
* moved component selection data structure out of dragpanel into a seperate module
* removed unused file (Thumbs.db)

Any help you can give in testing this release would be very much appreciated.

Thanks!

-Mike

Hey folks,

I've been working on the next WireMaster release, and I've got RC2 available here:
http://dreamingbits.com/wiremaster/WireMaster_0.46_installer_windows.exe

Please don't share this link with people since it's a private build and I don't want to leak this out into the wild yet. Can you please find some time to help test out the app and find bugs/problems before we release this? I realize it's a pain but we don't have a regular tester yet, so anything you can do to help would be appreciated, even if it's only 5-10 mins of testing. 

Jeff, here is the high level changelog for 0.46:
* fixed loading bug http://sourceforge.net/tracker/?func=detail&aid=2790114&group_id=179303&atid=888611
* draggable selections https://sourceforge.net/tracker/?func=detail&aid=2778354&group_id=179303&atid=888614
* draggable component toolbar https://sourceforge.net/tracker/?func=detail&aid=2796978&group_id=179303&atid=888614
* starting to implement a nicer look and feel

Thanks! Hope you're all doing well!

-Mike

On Wed, May 27, 2009 at 6:29 PM, mike rein <cov...@ya...> wrote:

>
> * Jeff, I've setup subversion hook so that you should receive emails when
> commits happen. Is this working correctly for you? If anyone else wants an
> email notification on sVn commits please let me know.

Yes, I'm getting the SVN notifications.  Thanks.

Hey folks, 

Sorry I haven't been in touch in a while, been very occupied here with work. There are a few developments with WireMaster, here they are:

* v0.46 is almost ready to go out, but needs some testing. It's mostly just a bug fix release, but it's also got some style changes that reflect some ideas I have around how to make the tool look a little more "slick". If anyone has any time to help test the release it would be a _huge_ help. If you don't have subversion setup or can't build the code, I've put a windows installer for 0.46 on my website: http://dreamingbits.com/wiremaster/WireMaster_0.46_installer_windows.exe

* Jeff, I've setup subversion hook so that you should receive emails when commits happen. Is this working correctly for you? If anyone else wants an email notification on sVn commits please let me know.

* Jeff, I integrated your icon into Wiremaster in v0.46. Looks good! :)

* I gave Softpedia permission to display WireMaster on their website. This won't change anything in how we work, they basically just link to sourceforge information that is publicly available. If you're curious, here's the link to WireMaster on their site: http://mac.softpedia.com/get/Developer-Tools/Wiremaster.shtml

Anyway, that's the bulk of what's going on. If you have any questions/comments/concerns/ideas/etc please feel free to share. Also if you have any spare time please try the v0.46 build and see if it causes any problems for you so we can push out this release soon. 

thanks all! :)

-Mike

Sorry for the delay in my response, folks. Comments are inline.

> Secondly, the build batch file will no longer work with the
> new packages (as I have no way of testing it, so I probably
> shouldn't edit it :). But you *could* use the ant build
> file :-) which works a treat. (Mike: did you want the jar to
> go straight to deploy/ as WireMaster.jar instead of
> dist/WireMaster-version.jar?)

Let's have Wiremaster run out of the deploy/ directory. So when building from source, rather than having it create jar file in src/, let's have it created in deploy. 

Jeff, what do you think about working with Zac to write up a small guide on how to build Wiremaster from Ant? I'm thinking a couple of paragraphs could probably accomplish this and it would be helpful to developers that aren't yet familiar with Ant or Wiremaster. 

> PS Mike: I left the other stuff in src/ because I don't
> want to delete it incase you want it there, otherwise can I
> delete it ? :).

As long as the build process is modified as mentioned above, sure. Might as well remove the redundancy. :)

-Mike

G'day,

As Mike gave me permission (and somewhat agreed :)). The source has been
restructured to use packages, the package name is "net.sf.wiremaster" and
"net.sf.wiremaster.component" for the components. Note the component package
is no longer upper-case, as this is confusing when dealing with classes.

Secondly, the build batch file will no longer work with the new packages (as
I have no way of testing it, so I probably shouldn't edit it :). But you
*could* use the ant build file :-) which works a treat. (Mike: did you want
the jar to go straight to deploy/ as WireMaster.jar instead of
dist/WireMaster-version.jar?)

Since all the files have changed, you'll probably have a conflict when you
check-in any files you have checked out, but do a `diff` and you'll see I
haven't changed much (so just reflect my changes in your new version of the
file).

PS Mike: I left the other stuff in src/ because I don't want to delete it
incase you want it there, otherwise can I delete it ? :). Also forcing
hardware rendering didn't speed up the grid at all (ran at the same, slow,
speed). I've tried on several Linux set-ups and distros. I'll attempt to
track this down. I might also see if I can come up with some user interface
ideas.

Cheers
Zac

Hi Priyanka!

> … Actually it should be
> “she” J
Oops, Sorry about that! :) 

> Well I am
> working on the right align text
> option right now and I need little help
> Mike. 
Sure, how can I help?

> I am nearly
> done with the right align
> thing, If you can send the latest code, I’ll make the
> changes and will
> send it back to you as soon as possible, 
Sounds good. 

> I apologize
> for the inconvenience. I’ll
> try to talk with the officials to get SVN as soon as
> possible. 
ok, I hope you aren't going to get in trouble for asking for subversion at work, but if you can get subversion working it will be easier for you to contribute in the future.

> I am really
> looking forward to work with
> you all!! 
ditto! curious, what are you in India? My old housemate is from New Delhi. I'm planning to take a trip from Goa to Nepal this fall. 

-Mike

> I'm glad you like the logos,
> Mike.  "SOLID B" is my pick, too.
Can you create an icon sized versions of "SOLID B" so that we can put them in the application itself, the installer, desktop shortcut, etc? Looking forward to replacing te existing java default icon. :)

> I'll definitely appreciate commit emails.  
I'm assuming you want the commit emails sent to gr...@gm...?

> The Tracker for the project will come in handy for me to
> keep up to date on changes, too.  Please use it to its
> fullest, especially the Bugs and Feature Requests lists.
agreed.  Jeff, can you go into the tracker and add any documentation tasks you think are needed? Zac, I'm assuming you are working on the Linux platform issues. If so can you assign that issue in the feature tracker to yourself? Priyanka is already working on the right aligned text feature, so I've assigned that to her. :)

Hi everyone,

It's great working with people from all over the world.
As told by Mike, I am a software engineer currently working in an IT services firm.
I completed my graduation last year and I stay in India. (GMT +5.5)

Well Mike one correction is needed - "Priyanka Bansal is a software engineer with experience in Swing and some Java2D.
He's offered to help with the coding."  ... Actually it should be "she" :)

Well I am working on the right align text option right now and I need little help Mike.
Actually am working from my company's system and I can't install subversion here.
I am nearly done with the right align thing, If you can send the latest code, I'll make the changes and will send it back to you as soon as possible,
then you can review it and tell the areas of improvement.

I am online for next 4 hrs, else I can do it on Monday.

I apologize for the inconvenience. I'll try to talk with the officials to get SVN as soon as possible.

I am really looking forward to work with you all!!

Thanks and Regards
Priyanka :)

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

I'm glad you like the logos, Mike.  "SOLID B" is my pick, too.

I'll definitely appreciate commit emails.  I can monitor them for anything
that affects the docs.  I don't want to maintain the change log; I'll leave
that to you and the other developers.  I'll gladly edit release notes for
grammar, style, and spelling, though.

The Tracker for the project will come in handy for me to keep up to date on
changes, too.  Please use it to its fullest, especially the Bugs and Feature
Requests lists.

Jeff

On Thu, May 14, 2009 at 11:55 PM, mike rein <cov...@ya...> wrote:

>
> Jeff,
>
> I like the logos! In my opinion, the solid set, item B looks the best. What
> do the rest of you guys think? We can vote on most popular choice.
>
> I gave you editor permission for some of the copy on the website (releases,
> news, forums,etc) so feel free to change any of that messaging if you feel
> it's lacking/out of date/etc.
>
> Regarding the commits, I agree we should never have blank log messages.
> They don't have to be long, but they should be descriptive and cover the
> major changes in the commit (I don't expect every comment to be an
> exhaustive list of changes.)
> If you're mainly after a rough changelog, happy to help with that.
>
>
> Also, I think it's possible to have an email sent out to people when
> commits are made, if any of you would like to be added to that alert list
> please let me know.. :)
>
> -Mike
>
>
> --- On Fri, 5/15/09, Jeff Mattfield <gr...@gm...> wrote:
>
> > From: Jeff Mattfield <gr...@gm...>
> > Subject: Re: [Wiremaster-general] getting started
> > To: wir...@li...
> > Date: Friday, May 15, 2009, 12:39 AM
> > Hi,
> >
> > Jeff here, a recently unemployed developer in the US who is
> > changing careers, working his way into technical writing.
> >
> >
> > I will tackle the documentation in the order in which Mike
> > listed
> > them--GSG, manual, web site.  If you have any suggestions
> > for the docs,
> > don't hesitate to bring them up.
> >
> > To help me keep the docs in sync with the application, I
> > ask everyone to use commit messages when checking in code.
> > Release notes come in handy, but I'd like to stay ahead
> > of them, if I can.
> >
> >
> > For additional visual appeal to the docs, I took the
> > liberty of creating a logo.  The images below show
> > different treatments of a W-and-M logo.  Let me know your
> > opinions about color and whether to use an outlined
> > "W" or "M" or neither.
> >
> >
> > http://img30.imageshack.us/my.php?image=logowirew.png
> > http://img41.imageshack.us/my.php?image=logowirem.png
> >
> > http://img269.imageshack.us/my.php?image=logosolid.png
> >
> > I also have in mind a logo that incorporates a wire-frame
> > globe if you find none of these appealing.
> >
> >
> > I'm excited to be part of this project, and I look
> > forward to working with you all.
> >
> > Jeff
> >
> >
> >
> > -----Inline Attachment Follows-----
> >
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensing option that enables
> >
> > unlimited royalty-free distribution of the report engine
> > for externally facing server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > -----Inline Attachment Follows-----
> >
> > _______________________________________________
> > Wiremaster-general mailing list
> > Wir...@li...
> > https://lists.sourceforge.net/lists/listinfo/wiremaster-general
> >
>
>
>
>
>

Jeff,

I like the logos! In my opinion, the solid set, item B looks the best. What do the rest of you guys think? We can vote on most popular choice.

I gave you editor permission for some of the copy on the website (releases, news, forums,etc) so feel free to change any of that messaging if you feel it's lacking/out of date/etc. 

Regarding the commits, I agree we should never have blank log messages. They don't have to be long, but they should be descriptive and cover the major changes in the commit (I don't expect every comment to be an exhaustive list of changes.)
If you're mainly after a rough changelog, happy to help with that.

Also, I think it's possible to have an email sent out to people when commits are made, if any of you would like to be added to that alert list please let me know.. :)

-Mike

--- On Fri, 5/15/09, Jeff Mattfield <gr...@gm...> wrote:

> From: Jeff Mattfield <gr...@gm...>
> Subject: Re: [Wiremaster-general] getting started
> To: wir...@li...
> Date: Friday, May 15, 2009, 12:39 AM
> Hi,
> 
> Jeff here, a recently unemployed developer in the US who is
> changing careers, working his way into technical writing.
> 
> 
> I will tackle the documentation in the order in which Mike
> listed
> them--GSG, manual, web site.  If you have any suggestions
> for the docs,
> don't hesitate to bring them up.
> 
> To help me keep the docs in sync with the application, I
> ask everyone to use commit messages when checking in code. 
> Release notes come in handy, but I'd like to stay ahead
> of them, if I can.
> 
> 
> For additional visual appeal to the docs, I took the
> liberty of creating a logo.  The images below show
> different treatments of a W-and-M logo.  Let me know your
> opinions about color and whether to use an outlined
> "W" or "M" or neither.
> 
> 
> http://img30.imageshack.us/my.php?image=logowirew.png
> http://img41.imageshack.us/my.php?image=logowirem.png
> 
> http://img269.imageshack.us/my.php?image=logosolid.png
> 
> I also have in mind a logo that incorporates a wire-frame
> globe if you find none of these appealing.
> 
> 
> I'm excited to be part of this project, and I look
> forward to working with you all.
> 
> Jeff
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> 
> unlimited royalty-free distribution of the report engine 
> for externally facing server and web deployment. 
> http://p.sf.net/sfu/businessobjects
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Wiremaster-general mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wiremaster-general
> 

Hi,

Jeff here, a recently unemployed developer in the US who is changing
careers, working his way into technical writing.

I will tackle the documentation in the order in which Mike listed them--GSG,
manual, web site.  If you have any suggestions for the docs, don't hesitate
to bring them up.

To help me keep the docs in sync with the application, I ask everyone to use
commit messages when checking in code.  Release notes come in handy, but I'd
like to stay ahead of them, if I can.

For additional visual appeal to the docs, I took the liberty of creating a
logo.  The images below show different treatments of a W-and-M logo.  Let me
know your opinions about color and whether to use an outlined "W" or "M" or
neither.

http://img30.imageshack.us/my.php?image=logowirew.png
http://img41.imageshack.us/my.php?image=logowirem.png
http://img269.imageshack.us/my.php?image=logosolid.png

I also have in mind a logo that incorporates a wire-frame globe if you find
none of these appealing.

I'm excited to be part of this project, and I look forward to working with
you all.

Jeff

Zac,

All good points. A few comments/questions:
* I don't have ant setup. I've used it very minimally and only a few times. Are there any special steps that I need to do to get this working?
* I'm assuming the ant config is now going to run everything from the deployment directory?
* I'm happy to add Linux/Mac OS X support, but let's keep in mind that given the type of software and the types of people that use this, we are looking at a large number of Windows users, followed by some Mac users, and finally Linux. Let's make sure we don't break the win32 installer, and that the windows build doesn't suffer. Not suggesting we'll do this, but it's easy to happen when the developers are mostly on Linux. :)

> Before getting stuck into the actual coding, I thought
> I'd set up an Apache Ant build script. I wrote one to
> mimic the current build.bat so the process is now uniform,
> and cross-platform. It's located in /trunk/build.xml
> 
> 
> There are a few additional reasons for using ant, the java
> compiler is bugged in the detection of changed files and
> often doesn't rebuild them (even though you've
> changed them) which can lead to some strange bugs. Anyway,
> once you've got ant the process is very simple.
> 
> 
> For a full build (run from src/)
> $ ant
> 
> The other targets for the build file are:
> $ ant compile
> $ ant dist
> $ ant clean
> 
> The dist target compiles also, so you don't need to
> call them more than once. (Note that $ is your prompt :)).
> Note also that the WireMaster-0.44.jar is created in dist/
> which you can then move to deploy/ (this could be changed to
> go straight to deploy, but we'll see what Mike says :))
> 
> 
> The compile will be "out of source", that is all
> the *.class files are compiled into build/ then jar'd
> into dist/
> 
> My ideas on restructuring the source to make it a bit more
> workable:
> 
> 1. Remove everything non-source related from /trunk/src/
> including "settings", "wireframes" and
> "icons". src/ should really be kept for the code.
> 
> 
> 2. Restructure the source directory to use
> "packages", such that the package name would be
> "net.sf.WireMaster". The standard is "The URL
> of the project reversed, i.e from "wiremaster.sf.net".
> This makes things a lot cleaner for compiling and also
> debugging, especially if you plan to have plugins in the
> future.
> 
> 
> In summary, the new "structure" would be:
> 
> src/
>   net/
>     sf/
>       WireMaster/
>         <all the wiremaster classes>
>         components/
>           <all the components>
> 
> 
> So, using a button in say WireMaster.java would look like:
> 
> package net.sf.wiremaster;
> 
> 
> import net.sf.wiremaster.components.*;
> 
> ...
> 
> Button but = new Button();
> 
> Also, I don't think it's a good idea checking
> binaries (or Wiremaster.jar) into SVN. As these change
> constantly and it makes the bandwidth / size of the repo
> rather high!
> 
> 
> Zac
>  
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY
> circumstances! Your
> production scanning environment may not be a perfect world
> - but thanks to
> Kodak, there's a perfect scanner to get the job done! With
> the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with
> all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Wiremaster-general mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wiremaster-general
> 

 > AF1: http://img24.imageshack.us/img24/5754/20090514194939800x600sc.png
I don't see any issues with this screen shot, it looks correct to me.

> AF2: http://img17.imageshack.us/img17/2444/20090514195026242x55scr.png
This looks like a problem with the button and label widths, probably too short given your screen size/resolution. We should probably adjust some of the UI components so they don't get cut off like this.

> And the window doesn't inherit the natural style of the
> users desktop (border wise). The window is also created in
> default 800x600 (EW).
800X600 was a design decision I made on purpose since it's a safe lowest common denominator for most computer screens these days. I'm open to some kind of screen resolution detection and size based on that, or some other solution. Thoughts?

> Also, my timezone is GMT + 10, how about everyone else?
I'm -5 GMT

Anyway, I forgot to show the artefacts, they're rather small, but the
biggest issue is the program is almost unusable with the grid on.

AF1: http://img24.imageshack.us/img24/5754/20090514194939800x600sc.png
AF2: http://img17.imageshack.us/img17/2444/20090514195026242x55scr.png

Look closely at both... the second one does have a title, I just didn't show
it in the picture :)

And the window doesn't inherit the natural style of the users desktop
(border wise). The window is also created in default 800x600 (EW).

Also, my timezone is GMT + 10, how about everyone else?

G'day,

Before getting stuck into the actual coding, I thought I'd set up an Apache
Ant build script. I wrote one to mimic the current build.bat so the process
is now uniform, and cross-platform. It's located in /trunk/build.xml

There are a few additional reasons for using ant, the java compiler is
bugged in the detection of changed files and often doesn't rebuild them
(even though you've changed them) which can lead to some strange bugs.
Anyway, once you've got ant the process is very simple.

For a full build (run from src/)
$ ant

The other targets for the build file are:
$ ant compile
$ ant dist
$ ant clean

The dist target compiles also, so you don't need to call them more than
once. (Note that $ is your prompt :)). Note also that the
WireMaster-0.44.jar is created in dist/ which you can then move to deploy/
(this could be changed to go straight to deploy, but we'll see what Mike
says :))

The compile will be "out of source", that is all the *.class files are
compiled into build/ then jar'd into dist/

My ideas on restructuring the source to make it a bit more workable:

1. Remove everything non-source related from /trunk/src/ including
"settings", "wireframes" and "icons". src/ should really be kept for the
code.

2. Restructure the source directory to use "packages", such that the package
name would be "net.sf.WireMaster". The standard is "The URL of the project
reversed, i.e from "wiremaster.sf.net". This makes things a lot cleaner for
compiling and also debugging, especially if you plan to have plugins in the
future.

In summary, the new "structure" would be:

src/
 net/
   sf/
     WireMaster/
       <all the wiremaster classes>
       components/
          <all the components>

So, using a button in say WireMaster.java would look like:

package net.sf.wiremaster;
>
> import net.sf.wiremaster.components.*;
>
> ...
>
> Button but = new Button();

Also, I don't think it's a good idea checking binaries (or Wiremaster.jar)
into SVN. As these change constantly and it makes the bandwidth / size of
the repo rather high!

Zac

hi Zac!

Few questions/comments:

can you send me some screen shots of the strange rendering artifacts you are encountering in linux? Sounds interesting :) 

Yes, I think the idea is that there would be some kind of "project" file as you described.

On the coding practices, I've tried to be as consistent as possible, but you may find some problems. Probably the 2 biggest conventions are tab indenting, and all brackets on individual lines. If you folks find any problems or lack of coding standards please feel free to make suggestions so we can fix them.

I'll try to come up with some mockups for a slicker UI, but I'm not an artist so they probably won't be beautiful. :)

On the issue tracker, I agree. I've been trying to use the issue tracker that is available here:
http://sourceforge.net/tracker/?limit=10&func=&group_id=179303&atid=888614

Also, if you folks would like to chat via Instant messenger I'm on aol instant messenger (MikeR1728) and yahoo im (covert_access). 

-Mike

--- On Wed, 5/13/09, Zac Sims <zac...@gm...> wrote:

From: Zac Sims <zac...@gm...>
Subject: [Wiremaster-general] getting started
To: Wir...@li...
Date: Wednesday, May 13, 2009, 10:35 PM

Hello,

I'm Zac :). I've never used mailing-lists before, so tell me if I'm doing it wrong.

> improve Mac OS X/Linux support - I haven't done much to make wiremaster
work on these platforms but friends tell me they've had some mixed
success getting it to run.
Sure. It's currently rather bugged as it is, when I said it "ran at 5FPS with the grid on", I meant it was very laggy. Some labels and buttons are also smaller than the text that is in them.

> Add Website diagramming - some UI people have asked for the ability to create a sitemap,
Sounds awesome, that means however that you should have support for "projects" that can have multiple pages, and perhaps generate a sitemap.

> more components - it would be great to provide a much richer set of
components, possibly in a way that would let people create their own
widgets
Perhaps some sort of vector based format would also be good, rather than bitmap controls.

> improved look and feel - I would *love* to come up with a slick user interface for this

Perhaps you could come up with a few mock-ups? (Done in WireMaster of course).

Secondly, is there some sort of coding convention you'd like us to follow?

Also, perhaps we should be using the feature/issue tracker on the sf.net page? We don't all want to be working on the same thing :-).

Zac

-----Inline Attachment Follows-----

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
-----Inline Attachment Follows-----

_______________________________________________
Wiremaster-general mailing list
Wir...@li...
https://lists.sourceforge.net/lists/listinfo/wiremaster-general

Hello,

I'm Zac :). I've never used mailing-lists before, so tell me if I'm doing it
wrong.

> improve Mac OS X/Linux support - I haven't done much to make wiremaster
work on these platforms but friends tell me they've had some mixed success
getting it to run.
Sure. It's currently rather bugged as it is, when I said it "ran at 5FPS
with the grid on", I meant it was very laggy. Some labels and buttons are
also smaller than the text that is in them.

> Add Website diagramming - some UI people have asked for the ability to
create a sitemap,
Sounds awesome, that means however that you should have support for
"projects" that can have multiple pages, and perhaps generate a sitemap.

> more components - it would be great to provide a much richer set of
components, possibly in a way that would let people create their own widgets
Perhaps some sort of vector based format would also be good, rather than
bitmap controls.

> improved look and feel - I would *love* to come up with a slick user
interface for this
Perhaps you could come up with a few mock-ups? (Done in WireMaster of
course).

Secondly, is there some sort of coding convention you'd like us to follow?

Also, perhaps we should be using the feature/issue tracker on the
sf.netpage? We don't all want to be working on the same thing :-).

Zac

Hey guys,

I want to take a few minutes to welcome all of you to the team, do a
quick round of introductions, and present a few potential work areas we
can start with.:) 

Introductions:

I'm Mike. I am the original creator of WireMaster and have been the sole developer so far. 

Jeff Mattfield has offered to help with our ongoing documentation effort. This is a large area, including:
* getting started guide
* user's manual
* web site

As you have probably seen, these areas are currently lacking in a big way, so looking forward to expanding on this.

Priyanka Bansal is a software engineer with experience in Swing and some Java2D. He's offered to help with the coding.

Zachary Sims is a software engineering student atMonash Uni in Melbourne, Australia. He has experience with Java, OpenGL, and C++. He's also offered to help with coding.

Babu Rajendran is a software engineer that has experience with JFC and Swing. As you may have guessed given his background, he's also interested in helping with the code. :)

So those are basic intros, feel free to mail the group and introduce yourself personally if you'd like to add anything. :)

subversion:
I'Zach made a good point in an email, sending .zip files around is a crappy way for multiple people to develop, so I've setup subversion and given all of you read and commit access to the subversion repository, which I've setup here: https://wiremaster.svn.sourceforge.net/svnroot/wiremaster
The trunk/ directory contains the most up to date code, which is currently 0.45 The current release is 0.44 which is tagged in the tags/ directory. I think we can
 keep the current version in trunk that is actively being developed, and branch/tag releases as necessary.

ideas for upcoming tasks/work:
As this is a volunteer project, I think it makes sense for you guys to pick and choose what you'd like to work on, as I would like to keep this project fun, enjoyable, and low stress. :) Here are a list of some ideas for features that I think might be good for the near term:

improve Mac OS X/Linux support - I haven't done much to make wiremaster work on these platforms but friends tell me they've had some mixed success getting it to run.Add Website diagramming - some UI people have asked for the ability to create a sitemap, where each page is a node in a tree that gets built graphically. each page in the tree could then be a seperate wireframe. This would be very helpful for building large sitesA user guide - there are several undocumented but handy features in wiremaster, such as holding down the ctrl key to select multiple objects, moving objects
 with arrow keys, etc. maybe when wiremaster starts for the first time we could put a link to this, and add it to the help menu
more components - it would be great to provide a much richer set of components, possibly in a way that would let people create their own widgetsspecific properties for certain widgets. (e.g., table components have properties like row, column that don't make sense for othere component types)improved look and feel - I would *love* to come up with a slick user interface for this, for example switching between wireframes could animate slide in/slide out, fade, converting the frames and dialogs to a nicer look (maybe like the iphone style black menus with white text, gradients, rounded corners, etc)improve the hand drawn renderer - this is meant to show that a wireframe is in the design stage and not a finished product, but the current draw by hand algorithm does not look very good. improving
 this algorithm would make it look more like a sketch, possibly using different Java2D brush strokes, paths, etc
Again, these are just ideas that I have thought of on some features that I think would be nice. There are several more on the feature tracker on wiremaster's sourceforge site. Given your backgrounds and interests, let's see if any of the above fit, and if not, feel free to suggest some new ones.

Anyway, this email is getting pretty long but I wanted to "get the ball rolling" and start a conversation. What do you guys think? Questions/comments/feedback/ideas sorely needed. :)

-Mike

This is a test email, first one for the WireMaster mailing list!

w00t

2009	Jan	Feb	Mar	Apr (1)	May (16)	Jun (4)	Jul	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

wiremaster-general Mailing List for WireMaster

wiremaster-general — all things wiremaster related