From mario at ruby-im.net  Wed Jun 11 04:31:16 2008
From: mario at ruby-im.net (Mario Steele)
Date: Wed, 11 Jun 2008 03:31:16 -0500
Subject: [Wxride-development] Moving discussions over to the Mailing List
Message-ID: <a4439dea0806110131j18a67cct7eff2bf53caf4bde@mail.gmail.com>

Hey Sean,

I'm officially going to move the discussions over to the Mailing List at
this time.  So from now on, any messages dealing with wxRIDE's development,
should be posted directly to the Mailing List.  Do not reply directly to me,
unless it is something that only warrants my attention.  Otherwise, all
discussion will be taking place on wxRIDE Development mailing list.  The
reason for the move, is cause I'm going to be getting more people involved.
I would also like you to join us on #wxruby, as I'm targeting that for now,
as our development channel, along with wxRuby.  I have setup a CIA Bot that
will notify of new updates to the SVN Repository, as well as a mailing list
setup specifically for commits only.  wxride-commits at rubyforge.org.  This
mailing list is strictly for SVN Updates done to the Repository, and will
not be used for conversation.  That is why we have wxride-users, and
wxride-development.

Thanks,

-- 
Mario Steele
http://www.trilake.net
http://www.ruby-im.net
http://rubyforge.org/projects/wxruby/
http://rubyforge.org/projects/wxride/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxride-development/attachments/20080611/4d1ca0a2/attachment.html>

From ukimi367 at gmail.com  Thu Jun 12 08:51:40 2008
From: ukimi367 at gmail.com (Sean)
Date: Thu, 12 Jun 2008 08:51:40 -0400
Subject: [Wxride-development] Moving discussions over to the Mailing List
In-Reply-To: <a4439dea0806110131j18a67cct7eff2bf53caf4bde@mail.gmail.com>
References: <a4439dea0806110131j18a67cct7eff2bf53caf4bde@mail.gmail.com>
Message-ID: <d2d056160806120551t58f6ca59t6b51639e1dafba28@mail.gmail.com>

Hi Mario,

I wanted to give you a quick update on the syntax.  I have been working on
the PHP syntax, but I am going to put that on the back burner for a little
while and add some easier syntaxes first.  SciTE doesn't actually have a PHP
properties file; rather, they lump it in with HTML, Javascript, and other
related HTML syntaxes.  As such, the code is quite long and complicated and
it requires I dive deeper into Scintilla and SciTE to understand the
subtleties better.  I will add some new syntaxes to the wxRIDE repository (I
am trying to do one a day), and also dive deeper into the Scintilla code in
parallel.

Any questions, comments, or concerns, please let me know.

Regards,
Sean



On 6/11/08, Mario Steele <mario at ruby-im.net> wrote:
>
> Hey Sean,
>
> I'm officially going to move the discussions over to the Mailing List at
> this time.  So from now on, any messages dealing with wxRIDE's development,
> should be posted directly to the Mailing List.  Do not reply directly to me,
> unless it is something that only warrants my attention.  Otherwise, all
> discussion will be taking place on wxRIDE Development mailing list.  The
> reason for the move, is cause I'm going to be getting more people involved.
> I would also like you to join us on #wxruby, as I'm targeting that for now,
> as our development channel, along with wxRuby.  I have setup a CIA Bot that
> will notify of new updates to the SVN Repository, as well as a mailing list
> setup specifically for commits only.  wxride-commits at rubyforge.org.  This
> mailing list is strictly for SVN Updates done to the Repository, and will
> not be used for conversation.  That is why we have wxride-users, and
> wxride-development.
>
> Thanks,
>
> --
> Mario Steele
> http://www.trilake.net
> http://www.ruby-im.net
> http://rubyforge.org/projects/wxruby/
> http://rubyforge.org/projects/wxride/
> _______________________________________________
> Wxride-development mailing list
> Wxride-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxride-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxride-development/attachments/20080612/364c1adb/attachment.html>

From ukimi367 at gmail.com  Thu Jun 19 01:21:10 2008
From: ukimi367 at gmail.com (Sean)
Date: Thu, 19 Jun 2008 01:21:10 -0400
Subject: [Wxride-development] wxRide Syntax Issues
Message-ID: <d2d056160806182221k77348823x1302a05c546e048d@mail.gmail.com>

Hi Mario,

As you know, I have been looking for a way to make EditorPage.rb syntax
agnostic.  Right now, there is the on_charadded(evt) method that is Ruby
specific as well as the other items I have already been working on.

So I have come up with the following that I believe will work.

Essentially I will make a module for each syntax: SyntaxRuby, SyntaxCpp,
etc.  The module will contain the code it does now to set keywords, colors,
etc, but will also contain its own on_charadded(evt) code that is specific
to the syntax.  By using Module#extend_object and Object#extend I should be
able make each instance of EditorPage have its own on_charadded(evt) method
that is specific to the syntax for that page.

I think that if this code works we will have made good in-roads on making
EditorPage syntax-independent.

Please take a look at the code and see if you think this will work.  If you
concur, then I will start coding up EditorPage.rb accordingly.

Best Regards,
Sean


Code:

# Testing ways to modify EditorPage.rb on the fly:

module SyntaxA

    def SyntaxA.extend_object(obj)
        @o = obj
        SyntaxA.get_syntax
    end

    def SyntaxA.get_syntax()
        puts "SyntaxA.get_syntax: #{@o}, type: #{@o.type}"
    end

end

module SyntaxB

    def SyntaxB.extend_object(obj)
        @o = obj
        SyntaxB.get_syntax
    end

    def SyntaxB.get_syntax()
        puts "SyntaxB.get_syntax: #{@o}, type: #{@o.type}"
    end

end

class Language

    attr_accessor :type

    def initialize (*args)
    end

    def call_syntax

        if @type == "X"
            self.extend(SyntaxA)
        elsif @type == "Y"
            self.extend(SyntaxB)
        end

    end

end

puts "Verify that object is passed by reference:"

x = Language.new
puts "x: #{x}"
x.type = "X"
x.call_syntax

y = Language.new
puts "y: #{y}"
y.type = "Y"
y.call_syntax

OUTPUT:

Wed Jun 18 21:24:23 Misc 1003 $: ruby evalTest4.rb
Verify that object is passed by reference:
x: #<Language:0xb7a540a8>
SyntaxA.get_syntax: #<Language:0xb7a540a8>, type: X
y: #<Language:0xb7a54044>
SyntaxB.get_syntax: #<Language:0xb7a54044>, type: Y
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxride-development/attachments/20080619/991e3e7a/attachment-0001.html>

From mario at ruby-im.net  Fri Jun 20 10:54:46 2008
From: mario at ruby-im.net (Mario Steele)
Date: Fri, 20 Jun 2008 09:54:46 -0500
Subject: [Wxride-development] wxRide Syntax Issues
In-Reply-To: <d2d056160806182221k77348823x1302a05c546e048d@mail.gmail.com>
References: <d2d056160806182221k77348823x1302a05c546e048d@mail.gmail.com>
Message-ID: <a4439dea0806200754m710c4b5aj91d093653586770e@mail.gmail.com>

Hello Sean,

On Thu, Jun 19, 2008 at 12:21 AM, Sean <ukimi367 at gmail.com> wrote:

> Hi Mario,


Yes, we have talked about this, and we are definately looking at this to be
a possible way.

Code:
>
> # Testing ways to modify EditorPage.rb on the fly:
>
> module SyntaxA
>
>     def SyntaxA.extend_object(obj)
>         @o = obj
>         SyntaxA.get_syntax
>     end
>
>     def SyntaxA.get_syntax()
>         puts "SyntaxA.get_syntax: #{@o}, type: #{@o.type}"
>     end
>
> end
>
> module SyntaxB
>
>     def SyntaxB.extend_object(obj)
>         @o = obj
>         SyntaxB.get_syntax
>     end
>
>     def SyntaxB.get_syntax()
>         puts "SyntaxB.get_syntax: #{@o}, type: #{@o.type}"
>     end
>
> end
>
> class Language
>
>     attr_accessor :type
>
>     def initialize (*args)
>     end
>
>     def call_syntax
>
>         if @type == "X"
>             self.extend(SyntaxA)
>         elsif @type == "Y"
>             self.extend(SyntaxB)
>         end
>
>     end
>
> end
>
> puts "Verify that object is passed by reference:"
>
> x = Language.new
> puts "x: #{x}"
> x.type = "X"
> x.call_syntax
>
> y = Language.new
> puts "y: #{y}"
> y.type = "Y"
> y.call_syntax


Yes, this is exactly how extend_object, and extend method works, you have
the general idea down, on how this will work.  Ofcourse, we don't need to
track the object when we go into extend_object().  It's pretty much a
message, to let us know when the object has been extended, and we can do our
meta magic on the object at this point.

For this method, for on_charadded(), this is great.  And having default
settings in the Module Syntax, also will be a good idea as well.  However, I
still want to be able to put on a code by code basis, the ability to add new
keywords, as well as different colors schemes as well.  For this, I still
believe that using YAML Dumped files for the schema's, and keywords would be
best done this way.  Keywords come to mind, due to the fact, that there are
libraries, and such, that we may want to syntax highlight on as well.  Which
would be useful to have.

I am going to have to go back in, and check the syntax highlighting we
currently have for Ruby, as when highlighting is done on a Instance
Variable, or a Class Variable, and a attached Method, it will syntax
highlight the entire section, up to the parenthisis, or the new line,
whichever.  So, I'll need to check into that, unless you want to take a
crack at it.

Thanks for the updates,

-- 
Mario Steele
http://www.trilake.net
http://www.ruby-im.net
http://rubyforge.org/projects/wxruby/
http://rubyforge.org/projects/wxride/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxride-development/attachments/20080620/26857596/attachment.html>

From ukimi367 at gmail.com  Fri Jun 20 20:47:35 2008
From: ukimi367 at gmail.com (Sean)
Date: Fri, 20 Jun 2008 20:47:35 -0400
Subject: [Wxride-development] wxRide Syntax Issues
Message-ID: <d2d056160806201747q3bbd8133o48e503486ecc07ad@mail.gmail.com>

Hi Mario,

Thanks for the email.  I am going to code up the Ruby syntax first just to
make sure I apply the extend_object correctly to EditorPage.rb before
proceeding with any of the other syntaxes.  Once I feel confident that I
have successfully brought in the on_charadded method correctly from the
module I will look into changing the syntax code to pull color and keyword
information from a YAML file instead of coded into the method.  Once I have
proven success using the Ruby syntax I will start to apply the necessary
changes to the other syntaxes.

Regards,
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxride-development/attachments/20080620/6d97d569/attachment.html>