hwx-users — HWX developers/users

[HWX] STC compile error! My mistake!

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

Sorry!
 =20
  The compile problem was my mistake! You can't compile STC library =
using=20
nmake -f makefile.vc FINAL=3D1
nmake -f makefile.vc WXMAKINGDLL=3D1 FINAL=3D1

  before compile
nmake -f makefile.vc WXUSINGDLL=3D1 FINAL=3D1

Graciliano M. P.

Re: [HWX] the beginnings of hwx.sf.net (and potential logo)

[Jouke V. <jo...@pv...>]

I like it very much....now for the content :)

DH wrote:

>http://crazyinsomniac.perlmonk.org/hwx.sf.net/    Has the image
>
>And a "sliced" up version of it is at ( aka "1" )
>http://crazyinsomniac.perlmonk.org/hwx.sf.net/hwx.sf.net.html
>
>And an idea for the layout (again with the slices, aka "2")
>http://crazyinsomniac.perlmonk.org/hwx.sf.net/hwx.sf.net.2.html
>
>Let me know what you think (it's ok to say it sucks )
>
>__________________________________________________
>Do you Yahoo!?
>New DSL Internet Access from SBC & Yahoo!
>http://sbc.yahoo.com
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Hwx-users mailing list
>Hwx...@li...
>https://lists.sourceforge.net/lists/listinfo/hwx-users
>

-- 

 -------------------------------------------------------------------- 
| Jouke Visser           | http://jouke.pvoice.org  (personal)       |
|                        | http://www.pvoice.org    (pVoice & pStory)|
| Perl GUI Geek          | http://wxperl.pvoice.org (wxPerl)         |
 -------------------------------------------------------------------- 

[HWX] the beginnings of hwx.sf.net (and potential logo)

[DH <cra...@ya...>]

http://crazyinsomniac.perlmonk.org/hwx.sf.net/    Has the image

And a "sliced" up version of it is at ( aka "1" )
http://crazyinsomniac.perlmonk.org/hwx.sf.net/hwx.sf.net.html

And an idea for the layout (again with the slices, aka "2")
http://crazyinsomniac.perlmonk.org/hwx.sf.net/hwx.sf.net.2.html

Let me know what you think (it's ok to say it sucks )

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [HWX] Some remarks already

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> Hi Graciliano,
>
> OK, let's summarize it:
>
> 1. If I understand you correctly, the GML specification is not finished
> yet and since it's one of the core components of HWXperl this is one of
> the more important tasks.
> 2. Your aim for HWXperl is to be multiplatform. I have a linux box to
> try to get it to work, so I'll work on that. I also got two old SUN
> Solaris boxes a few weeks ago, and I'll see if -after I get them to work
> at all- I can get it to work on that too.
This will be good. I think that if you can compile HWXperl on linux and
enable the module wxPerl on that too everything will work.

> 3. I'll develop the GUI Builder, which will be something like "The GUI
> Loft" - a designtool for Win32::GUI. It will output GML and/or XRC with
> Perlscripts. That way it won't be dependent on HWXperl. If I decide now
> to aim at both output formats, I won't have a problem later on when I
> decide to add XRC and have to hack it into the code.
About the builder, I haven't tested "The GUI Loft" yet, but I want something
very easy, more close to Delphi and DreamWaver, but of course that we are
open to better ideas.

> 4. I'll also try to create the debugger.
This is very good.

>
> I think I'll have enough to do working on points 2, 3, and 4 and let you
> guys work on GML, since you're already into that.
For me this is OK.

>
> We'll keep in touch!
>

Graciliano M. P.

Re: [HWX] Some remarks already

[Jouke V. <jo...@pv...>]

Hi Graciliano,

OK, let's summarize it:

1. If I understand you correctly, the GML specification is not finished 
yet and since it's one of the core components of HWXperl this is one of 
the more important tasks.
2. Your aim for HWXperl is to be multiplatform. I have a linux box to 
try to get it to work, so I'll work on that. I also got two old SUN 
Solaris boxes a few weeks ago, and I'll see if -after I get them to work 
at all- I can get it to work on that too.
3. I'll develop the GUI Builder, which will be something like "The GUI 
Loft" - a designtool for Win32::GUI. It will output GML and/or XRC with 
Perlscripts. That way it won't be dependent on HWXperl. If I decide now 
to aim at both output formats, I won't have a problem later on when I 
decide to add XRC and have to hack it into the code.
4. I'll also try to create the debugger.

I think I'll have enough to do working on points 2, 3, and 4 and let you 
guys work on GML, since you're already into that.

We'll keep in touch!

-- 

 -------------------------------------------------------------------- 
| Jouke Visser           | http://jouke.pvoice.org  (personal)       |
|                        | http://www.pvoice.org    (pVoice & pStory)|
| Perl GUI Geek          | http://wxperl.pvoice.org (wxPerl)         |
 -------------------------------------------------------------------- 

Re: [HWX] Some remarks already

[Jouke V. <jo...@pv...>]

> About the Win32 version, you can compile HWXperl on Linux too. Just get the
> module source from CVS. It need some changes for the linux version that I
> noly made for Win32, just look at Changes.HWX and see what need to be done
> for linux. The bigger problem will be with the extra modules and wxPerl,
> since it need wxWindows compiled. If you can help in the linux part will be
> very good. I have a linux here, got one PC just for HWX on linux, but I
> don't have time to see this now! Realy don't have!!!
I'll have a go to try to get it all to work on Linux.

> HWX has only 2 month of life! I think that first we need to develope it, and
> after create the pod, since during the development time a lot of thing can
> change in the structure (is a new thing, not very defined yet). I started to
> create the files of GML and HWX with the pod, but I cut it off since I
> always need to rewrite them!
I understand. However, I think it would be wise to add comments in your 
code to let other developers understand what's going on in the code...

>>4. You refer to HPL. Maybe that is where the 'H' comes from, but I don't
>>have the slightest idea what it is...can you enlighten me?
> 
> Yes.
...but what *is* HPL? What is the relationship between HWX and HPL?

> HWXperl doesn't have for plus only the DotRef. It has the tool PerlBin, this
> need to recompile the binarys of Perl to be enabled, and are a very useful
> tool!
OK, that's an obvious improvement. On the other hand, just a suggestion 
that comes to mind: why not send your idea about PerlBin to the p5p 
(Perl 5 Porters) so it might be a standard part of Perl? If that will 
happen, every perl installation has the possibility of creating 
standalone executables. That would remove the need for a different Perl 
flavour and would make the project a lot less complicated and more 
attractive to use.

> Well, you can be right in one part. But HWXperl is to run HWX apps, it will
> work in the enverioment HWX, this enverioment need to be equal in any OS,
> Perl can change a lot in different OS. The idea of create HWXperl is to have
> a Perl designed for PORTABLE GUI applications. And HWXperl is not only for
> developers, is for the enduser, that doesn't understand anything of Perl,
> compilers, modules, anything. It will just install HWXperl, like a DirectX,
> to run the App. The instal tool of HWX apps will see if the machine have HWX
> installed, if not it install it from the internet, and after this the app.
This is where I can't follow you. Are you saying that Perl -as it is 
currently- is different in different operating systems? That would be 
new to me.
HWX being a development environment for portable GUI applications in 
Perl sounds like THE idea. I think that goal can be reached in a number 
of different ways. I think taking Perl as it is itself simplifies the 
matter. Of course that also takes Wx as the GUI of choice. GML sounds 
like a great plan too. If we had a GUI Design tool, we'd be a step 
further. After that a full-featured IDE can be built.
PerlBin as a complementary tool is great too. Maybe it is an idea to 
develop PerlBin like Perl2Exe (by indigostar software) is done: release 
it in a kind of binary form per Perl release. PerlBin for ActiveState 
Perl build 633 for Windows, PerlBin for Perl 5.6.1 for Linux, etc.
And another idea is to develop a Perl Debugger with Wx as a part of the 
IDE. It shouldn't be too hard to do this using Devel::ptkdb as an example.

Another thing I don't understand is how you think endusers will use 
HWXperl. I don't see how endusers will develop GUI applications.

>>I think it would be wiser to enable anyone to use the different parts of
>>HWX's IDE *without* forcing them to use another Perl and let them decide
>>for themselves if they want to use the new interpreter.
> 
> Well, I'm doing this too, the DotRef for example, I don't use inside the
> modules, it will be used just for the end user. But the problem is: is very
> simple to use the dotref to control the objects, and I think that any
> developer of HWX apps will use it, and when the app goes out, the end user
> need DotRef too to run the app. But if a developer want to make a HWX app
> that works on any Perl version, it just use the basic things, that exist in
> the other Perl too, and it's free to install HWX, GML and wxPerl in any
> Perl. But the non-hwx-Perl that will run the HWX app, need to be configured
> by someone that understand of Perl and Modules, not a normal end user. And
> if you think, one of the bigger problem of Tk is this, it need to be
> instaled on Perl first. And GUI was created to be a easy thing to use, and
> can't be a hard thing to install, or the peoples don't use your app.
OK. Let's agree we disagree on this :). I don't see endusers using 
HWXperl or any Perl at all. Even less the possibility of a developer 
adjusting the code of the enduser to make it run on a normal Perl 
distro. At least I know I won't use the dot notation if I don't have to 
until Perl 6 comes out :)

> What we need to do is to enable HWXperl in any machine that want to run HWX
> apps, and any user need to be enabled to install it (well, the installation
> will be automatic). And our mission is bigger than just delivery a Perl with
> the same resource in any OS, it need to have module for GUI. For default
> Perl doesn't have anything for GUI, and is hard to get a standart perl and
> turn it on a platform for GUI apps (and portable), imagine ask for each end
> user, that just want to run or test the app, to do this by hand. You need to
> know that the majority of users will be of end users, peoples than don't
> know what is Perl. If the developer want to create a HWX app, it get HWX,
> that have a lot of tools for development. The end user just get the App, it
> don't need to know if it works with HWX, Perl, wxPerl, wxWindows, GML, or
> anything, it just want the app.
This is absolutely true. The important keyword here is PerlBin. Not the 
change of the dotsyntax. That dotsyntax will come in Perl 6. It's not 
something in Perl 5. That's my opinion.
If you're able to compile your script, you can distribute it to any user 
without him or her having to install all kinds of Perlmodules, or even 
perl itself. That's all there is to it.
Making it easier to develop GUI applications in Perl takes a good and 
complete IDE, in my idea containing a good editor, GUI design tool, 
compiler (PerlBin), debugger and maybe projectmanager.

If you feel I disagree with you too strongly to join the project, I'd 
understand. I'll still build a GUI design tool, and try to make it 
compatible with your project. If you still want me to join, I'd be very 
happy to!

Regards,

Jouke Visser

Re: [HWX] Some remarks already

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> I downloaded the current alpha release today on my linux box and haven't
> bothered yet to try to install it there, since you advertise it as a
> Win32 thing. I'll try it at home on my WinXP box asap. However, I have
> some remarks/questions already:
About the Win32 version, you can compile HWXperl on Linux too. Just get the
module source from CVS. It need some changes for the linux version that I
noly made for Win32, just look at Changes.HWX and see what need to be done
for linux. The bigger problem will be with the extra modules and wxPerl,
since it need wxWindows compiled. If you can help in the linux part will be
very good. I have a linux here, got one PC just for HWX on linux, but I
don't have time to see this now! Realy don't have!!!

> 1. Why is the project called HWX? the Wx part is clear...why the 'H'?
Yes, WX comes from wxWindows, H, well, I put because in the last thing that
I have developed I used the H (Hyper) to start it (HPL). Maybe Hyper is to
much, but I need to put something in the place of the H! ;-)
But I think that HWX is a good name.

> 2. Where is the documentation? There is *no* code documentation in the
> HWX and GML modules at all. How are new developers supposed to
> understand what it does?
HWX has only 2 month of life! I think that first we need to develope it, and
after create the pod, since during the development time a lot of thing can
change in the structure (is a new thing, not very defined yet). I started to
create the files of GML and HWX with the pod, but I cut it off since I
always need to rewrite them!

> 3. Is there a specification of GML? I've seen some quick examples in
> your postings, but there must be more.
It goes to have! But first it need to be more defined, stable.

> 4. You refer to HPL. Maybe that is where the 'H' comes from, but I don't
> have the slightest idea what it is...can you enlighten me?
Yes.

> 5. I personally feel that it's unwise to distribute a modified version
> of Perl. Why -except from the reason you mentioned to be able to use the
> dotref- would anyone want to use this Perl version?
HWXperl doesn't have for plus only the DotRef. It has the tool PerlBin, this
need to recompile the binarys of Perl to be enabled, and are a very useful
tool!

> This would imply (I think) that anyone who wants to use any part of the
> HWX IDE should download HWXperl, and throw away their existing perl
> installation. A lot of people like their distribution as it is, and
> won't bother using HWX's modified Perl.
Well, you can be right in one part. But HWXperl is to run HWX apps, it will
work in the enverioment HWX, this enverioment need to be equal in any OS,
Perl can change a lot in different OS. The idea of create HWXperl is to have
a Perl designed for PORTABLE GUI applications. And HWXperl is not only for
developers, is for the enduser, that doesn't understand anything of Perl,
compilers, modules, anything. It will just install HWXperl, like a DirectX,
to run the App. The instal tool of HWX apps will see if the machine have HWX
installed, if not it install it from the internet, and after this the app.

>
> I think it would be wiser to enable anyone to use the different parts of
> HWX's IDE *without* forcing them to use another Perl and let them decide
> for themselves if they want to use the new interpreter.
Well, I'm doing this too, the DotRef for example, I don't use inside the
modules, it will be used just for the end user. But the problem is: is very
simple to use the dotref to control the objects, and I think that any
developer of HWX apps will use it, and when the app goes out, the end user
need DotRef too to run the app. But if a developer want to make a HWX app
that works on any Perl version, it just use the basic things, that exist in
the other Perl too, and it's free to install HWX, GML and wxPerl in any
Perl. But the non-hwx-Perl that will run the HWX app, need to be configured
by someone that understand of Perl and Modules, not a normal end user. And
if you think, one of the bigger problem of Tk is this, it need to be
instaled on Perl first. And GUI was created to be a easy thing to use, and
can't be a hard thing to install, or the peoples don't use your app.

HWXperl has the tool PerlBin, to create a binary and publish your app
without the need of Perl instaled on the target machine.

> I know I'm critisizing, but I don't mean to offend you. Maybe if the
> reasons are clear to me I agree with the way it is now, but as I see it
> now, it doesn't seem logical.
I'm always open for ideas, I like what you say, you open a very good point.

What you need to know is the vision that I have for HWX apps. They need to
be very easy to be developed, and very easy to be instaled, or they can't be
portables. Perl is an amazing language, for me is the best, very easy and
let the user to be free to use the resource that it want, it let the mind
free. But Perl has a problem, it competes with languages that made a lot of
thing to turn more easy for the user with low knowledge. Perl for example,
wasn't very famous on Win32 like Linux, ActiveState made a good work, but
Perl was in "any" version of Linux, and we need to know that Perl wasn't in
any machine.

What we need to do is to enable HWXperl in any machine that want to run HWX
apps, and any user need to be enabled to install it (well, the installation
will be automatic). And our mission is bigger than just delivery a Perl with
the same resource in any OS, it need to have module for GUI. For default
Perl doesn't have anything for GUI, and is hard to get a standart perl and
turn it on a platform for GUI apps (and portable), imagine ask for each end
user, that just want to run or test the app, to do this by hand. You need to
know that the majority of users will be of end users, peoples than don't
know what is Perl. If the developer want to create a HWX app, it get HWX,
that have a lot of tools for development. The end user just get the App, it
don't need to know if it works with HWX, Perl, wxPerl, wxWindows, GML, or
anything, it just want the app.

Graciliano M. P.

[HWX] Some remarks already

[Jouke V. <jo...@pv...>]

Hello,

I downloaded the current alpha release today on my linux box and haven't 
bothered yet to try to install it there, since you advertise it as a 
Win32 thing. I'll try it at home on my WinXP box asap. However, I have 
some remarks/questions already:

1. Why is the project called HWX? the Wx part is clear...why the 'H'?
2. Where is the documentation? There is *no* code documentation in the 
HWX and GML modules at all. How are new developers supposed to 
understand what it does?
3. Is there a specification of GML? I've seen some quick examples in 
your postings, but there must be more.
4. You refer to HPL. Maybe that is where the 'H' comes from, but I don't 
have the slightest idea what it is...can you enlighten me?
5. I personally feel that it's unwise to distribute a modified version 
of Perl. Why -except from the reason you mentioned to be able to use the 
dotref- would anyone want to use this Perl version?
This would imply (I think) that anyone who wants to use any part of the 
HWX IDE should download HWXperl, and throw away their existing perl 
installation. A lot of people like their distribution as it is, and 
won't bother using HWX's modified Perl.

I think it would be wiser to enable anyone to use the different parts of 
HWX's IDE *without* forcing them to use another Perl and let them decide 
for themselves if they want to use the new interpreter.

I know I'm critisizing, but I don't mean to offend you. Maybe if the 
reasons are clear to me I agree with the way it is now, but as I see it 
now, it doesn't seem logical.

Cheers!

-- 

 -------------------------------------------------------------------- 
| Jouke Visser           | http://jouke.pvoice.org  (personal)       |
|                        | http://www.pvoice.org    (pVoice & pStory)|
| Perl GUI Geek          | http://wxperl.pvoice.org (wxPerl)         |
 -------------------------------------------------------------------- 

Re: [HWX] Joining the team

[DH <cra...@ya...>]

all right, all right, i'll join the team.
I can work on the pod ;)(for now)

One thing i wish to do is to take care of "PerlBin".
I'll try and get perlcompiler renamed perlbin,
and sell it as a subproject of hwxperl.
I think this'd be better so we don't have two projects
doing the same thing.
I think perlbin warrants being separated from
hwxperl as an extra of the hwxperl project
cause perlbin is not the primary goal.

Anyway, i'm crazyinsomniac on sourceforge, add me to the list


--- "Graciliano M. P. (Virtua Sites)" <gm...@vi...> wrote:
> > Hi Graciliano,
> >
> >  From [podmaster] I heard of your initiative, which you call 'HWXperl'.
> HWXperl is only the interpreter for HWX apps. More things for HWX will come,
> like the HWXeditor and tools, like PerlBin.
> 
> > And I must say that it completely complements the ideas I had of
> > building a GUI design tool for wxPerl. In fact I spoke with
> > [jplindstrom] (Johan Lindstrom), the author of 'The GUI Loft', which is
> > a GUI designtool for Win32::GUI about his efforts at YAPC::Europe, to
> > get the idea how to build something for wxPerl myself.
> >
> > This HWXperl project is just what wxPerl needs in my opinion. I would be
> > very happy to join the team to work on the GUI Design tool.
> I'm very happy too. This HWX project, specially the GML format, is becoming
> a fever, but I'm looking for developers, and the majority has the profile of
> users. Now we have in the development team 3 peoples, counting with me.
> Podmaster was interested too, but I think that it want to develope the
> perlcompiler project, using the PerlBin tool of HWX for this, if you can
> talk with him to help in HWX will be good too.
> 
> Now Thiago, the other developer from Brazil, was working in the Web Site. I
> asked for him something very simple, but functional.
> 
> >
> > I was thinking about what talk to give next at the German Perl Workshop
> > or YAPC::Europe 2003, and now I have found the right subject: I'll tell
> > Europe about this project as a complementary project to wxPerl!
> When will be the next event? Will be interesting to have HWX more stable
> until that.
> 
> > Please let's join forces and let me join your team!
> Of course! Send me your name and e-mail to put in the author list.
> 
> To work in the project use the module release of CVS, on SF. Now we are
> porting the controls to GML. I think that the best way to start is porting
> the control Wx::Button. Marcus, from Germany too, was doing this too, but
> use it to understand the GML and HWX structure for the objects, since it's
> very simple. Talk with Marcus, it can help you with the tips to port the
> controls.
> 
> In this week I will put the TODO file in the CVS, it will be generated from
> the site. And a doc of how to port a control to GML will be done too. But
> until that, take a look in the source of the module GML and HWX. And of
> course, try to find more peoples to the project. :-)
> 
> Graciliano M. P.
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Hwx-users mailing list
> Hwx...@li...
> https://lists.sourceforge.net/lists/listinfo/hwx-users


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [HWX] Joining the team

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> Hi Graciliano,
>
>  From [podmaster] I heard of your initiative, which you call 'HWXperl'.
HWXperl is only the interpreter for HWX apps. More things for HWX will come,
like the HWXeditor and tools, like PerlBin.

> And I must say that it completely complements the ideas I had of
> building a GUI design tool for wxPerl. In fact I spoke with
> [jplindstrom] (Johan Lindstrom), the author of 'The GUI Loft', which is
> a GUI designtool for Win32::GUI about his efforts at YAPC::Europe, to
> get the idea how to build something for wxPerl myself.
>
> This HWXperl project is just what wxPerl needs in my opinion. I would be
> very happy to join the team to work on the GUI Design tool.
I'm very happy too. This HWX project, specially the GML format, is becoming
a fever, but I'm looking for developers, and the majority has the profile of
users. Now we have in the development team 3 peoples, counting with me.
Podmaster was interested too, but I think that it want to develope the
perlcompiler project, using the PerlBin tool of HWX for this, if you can
talk with him to help in HWX will be good too.

Now Thiago, the other developer from Brazil, was working in the Web Site. I
asked for him something very simple, but functional.

>
> I was thinking about what talk to give next at the German Perl Workshop
> or YAPC::Europe 2003, and now I have found the right subject: I'll tell
> Europe about this project as a complementary project to wxPerl!
When will be the next event? Will be interesting to have HWX more stable
until that.

> Please let's join forces and let me join your team!
Of course! Send me your name and e-mail to put in the author list.

To work in the project use the module release of CVS, on SF. Now we are
porting the controls to GML. I think that the best way to start is porting
the control Wx::Button. Marcus, from Germany too, was doing this too, but
use it to understand the GML and HWX structure for the objects, since it's
very simple. Talk with Marcus, it can help you with the tips to port the
controls.

In this week I will put the TODO file in the CVS, it will be generated from
the site. And a doc of how to port a control to GML will be done too. But
until that, take a look in the source of the module GML and HWX. And of
course, try to find more peoples to the project. :-)

Graciliano M. P.

[HWX] Joining the team

[Jouke V. <jo...@pv...>]

Hi Graciliano,

 From [podmaster] I heard of your initiative, which you call 'HWXperl'. 
And I must say that it completely complements the ideas I had of 
building a GUI design tool for wxPerl. In fact I spoke with 
[jplindstrom] (Johan Lindstrom), the author of 'The GUI Loft', which is 
a GUI designtool for Win32::GUI about his efforts at YAPC::Europe, to 
get the idea how to build something for wxPerl myself.

This HWXperl project is just what wxPerl needs in my opinion. I would be 
very happy to join the team to work on the GUI Design tool.

I was thinking about what talk to give next at the German Perl Workshop 
or YAPC::Europe 2003, and now I have found the right subject: I'll tell 
Europe about this project as a complementary project to wxPerl!

Please let's join forces and let me join your team!

-- 

 -------------------------------------------------------------------- 
| Jouke Visser           | http://jouke.pvoice.org  (personal)       |
|                        | http://www.pvoice.org    (pVoice & pStory)|
| Perl GUI Geek          | http://wxperl.pvoice.org (wxPerl)         |
 -------------------------------------------------------------------- 

[HWX] Re: Can I pass off PerlBin as perlcompiler.sf.net? (and a small contribution)

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> Hi.
> I've compiled perl5.6.1 with the changes you made
> to runperl.c and miniperlmain.c
> and after realinzing I need a binary called hwxperl,
> I edited the Makefile.
You can change PerlBin (perlbin.pl) to use any name for the binary. Note,
that this perlbin was for Win32, since it looks for hwxperl.exe, for other
OS you just cut the .exe.

> I was able to successfully use PerlBin.
Cool!

>
> However, now I have a question,
> can I have permission to abstract PerlBin into
> the perlcompiler project?
> ( i have read Licence, but thought I'd give you a heads up )
You are totally free to use it in your project. I just ask to put my name in
the source and some reference to the HWX project in SF will be good too. And
of course, kip this part of your project free and Open Source. When it's
done let me know how is doing your project :-)

Will be good if you improve PerlBin with new things. One of them is link the
binary with Zlib to compress the script and the perl/lib inside the binary.
We of the HWX project will do this, but you can help too. Get the Zlib
module for Perl, or just Zlib source (I don't remember what have this), you
will see inside the source some C files and examples. One of them is to make
an autoextractor, or something like that.

>
> And now for the small contribution.
> $size_mark_re = $size_mark ;
> $size_mark_re =~ s/([^\w=#-])/\$1/gs ; ...
>
> if ($binlog !~ /$size_mark_re/s) {
> print "** The perl binary was not from HWXperl!\n $perl_bin\n" ;
> exit;
> }
>
> is better written as
>
> if( $binlog !~ /\Q$size_mark\E/s ) { ...
>
> \Q\E is basically quotemeta, see perldoc -f quotemeta, perldoc perlop
Well, we always have something to learn with Perl! Thanks.

Graciliano M. P.

[HWX] Can I pass off PerlBin as perlcompiler.sf.net? (and a small contribution)

[DH <cra...@ya...>]

Hi.
I've compiled perl5.6.1 with the changes you made 
to runperl.c and miniperlmain.c
and after realinzing I need a binary called hwxperl,
I edited the Makefile.

I was able to successfully use PerlBin.

However, now I have a question,
can I have permission to abstract PerlBin into
the perlcompiler project?
( i have read Licence, but thought I'd give you a heads up )

And now for the small contribution.
  $size_mark_re = $size_mark ;
  $size_mark_re =~ s/([^\w=#-])/\\$1/gs ; ...
  
  if ($binlog !~ /$size_mark_re/s) {
    print "** The perl binary was not from HWXperl!\n   $perl_bin\n" ;
    exit;
  }

is better written as

  if( $binlog !~ /\Q$size_mark\E/s ) { ...

\Q\E is basically quotemeta, see perldoc -f quotemeta, perldoc perlop

Nice job guys.


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

[HWX] Alpha Release 101c

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

The Alpha Release 101c was published on sourceforge
http://sourceforge.net/project/showfiles.php?group_id=3D55705

News:

  - New tool CopyLib.
  - Cache of gml parser.
  - Added lib LWP to load .gml files from internet.
  - New GML objects:
    * activex
    * activex_ie
    * boxsizer
    * flexgridsizer
    * font
    * gridsizer
    * menu
    * menubar
    * menuitem
    * sizer
    * staticbox
    * staticboxsizer
    * taskbaricon
    * textctrl
    * timer

Graciliano M. P.

[HWX] CVS Update

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

News on HWX CVS.

Sizer wrapped! The Boxsizer, StaticBoxsizer, GridSizer and FlexGridSizer was
enabled now, to use just put the objects inside a sizer block and set the
sizer options on each object:

    <staticboxsizer title="StaticBoxSizer Test" fit=1>
      <textctrl text='...' sizer="borderstyle=all ; border=10 ;
orient=expand ; align=center ; resize=0">
      <textctrl text='...' sizer="borderstyle=all ; border=10 ;
orient=expand ; align=center ; resize=1">
    </staticboxsizer>

    <gridsizer autocells>
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
    </gridsizer>

    <flexgridsizer rows=2 cols=2>
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand; flexrow ; flexcol">
      <textctrl text="..." sizer="borderstyle=all ; border=5 ;
orient=expand">
    </flexgridsizer>

Added the font tag (htmlstyle) on TextCtrl contents:

<textctrl htmlstyle size='500,400' multiline=1 font="face:Verdana ; size=10
; italic ; color: #FF0000" +>
Font Test!
bla bla bla
X<font color='0000FF' bgcolor='000000'>bla
<font color='00FF00'>bla</font>
bla</font>X
bla bla <b>bla</b>
</textctrl>

Send your suggestions and opinion about the new tags!

Enjoy,
Graciliano M. P.

[HWX] Alpha release

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

The alpha release of HWXperl is out! You can get it at
http://sourceforge.net/project/showfiles.php?group_id=55705&release_id=10794
2
HWXperl is only the interpreter for the HWX applications and the
enverioment.

This show the basics of the HWX enverioment, including GML (GUI Markup
Language),
the new extra resources added in the Perl interpreter, like PerlBin, that
allow the end user to
create a binary for the script without a compiler, just using the normal
Perl binarys.

HWXperl has new resources in the Perl syntax too, like the DotRef, that
allow things like that:

obj.frame.MyFrame.Show(1) ;

With this is more easy to find your object, you just need to know the ID,
and all the OO
commands are enable before it. You can use this to get the reference
variable of the boject too:

$frame = obj.frame.MyFrame ;

All of this works in the native syntax of Perl, this is not a filter module,
and are enabled inside
eval() and in the Check Syntax.

Graciliano M. P.