In fact, I have to draw my screen dynamically.
I explain.
In OpenERP, we use the xml files to describe the layout of our views,
with these xml files, we can create easily our screens.
For example: Here is the xml description of a screen
This xml descri
Sorry, thank you for your help
I’m not sure if I was able to help!
When I asked “what are you trying to do,” I meant: “what does the UI
you are trying to create look like?” NSMatrix is only appropriate for
certain, very limited interfaces. Otherwise you’ll need to roll your
own, or play i
Sorry, thank you for your help
On 08 Apr 2009, at 20:40, Benjamin Stiglitz wrote:
Question, I would like to know if there is a "cocoa like" of the
GtkTable widget
http://pygtk.org/pygtk2tutorial/sec-PackingUsingTables.html
NSMatrix, sort of.
To quote every other post on cocoa-dev: what a
If you know OpenERP (www.openerp.com), I write a new client for this
project,
On 08 Apr 2009, at 20:40, Benjamin Stiglitz wrote:
Question, I would like to know if there is a "cocoa like" of the
GtkTable widget
http://pygtk.org/pygtk2tutorial/sec-PackingUsingTables.html
NSMatrix, sort of.
Question, I would like to know if there is a "cocoa like" of the
GtkTable widget
http://pygtk.org/pygtk2tutorial/sec-PackingUsingTables.html
NSMatrix, sort of.
To quote every other post on cocoa-dev: what are you trying to do?
-Ben___
MacRuby-deve
When doing force_encoding, convert to a ByteString in the old
encoding, then try to convert to an NSString in the new encoding.
If we succeed, great. If not, leave as a tagged ByteString (and
probably whine about it).
That's actually wrong. All force_encoding does is change the
encoding a
Hi,
Question, I would like to know if there is a "cocoa like" of the
GtkTable widget
http://pygtk.org/pygtk2tutorial/sec-PackingUsingTables.html
Regards,
Stephane
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.maco
Vincent Isambart wrote:
the test_string tests in Ruby 1.9 repository do seem to mostly function
You mean test/ruby/test_m17n.rb, test/ruby/test_m17n_comb.rb,
test/ruby/test_io_m17n.rb and test/ruby/enc/test_*.rb?
test/ruby/test_string.rb does not contain anything m17n related.
We simply could
You are not the only person to have problems with XCode. My
own (limited) experience with it leads me to believe that it
requires the user to memorize a bunch of magic locations and
actions, all visually based. So, it doesn't work well for a
developer who likes to have everything laid out as text
I see occasional references of tutorials on the list, and I look
forward to their appearance with eagerness. But I fear that their
usefulness may be be greatly reduced, as have so many in the past, by
their attachment to XCode. I do not know whether XCode is a good or a
bad thing for deve
I'll be in Panamá for a few days, but I'll look at that when I'll come
back next week. If you feel more comfortable writing your article in
French, I'd be glad to get it translated.
-Matt
Sent from my iPhone
On Apr 8, 2009, at 2:19, Stéphane Wirtel
wrote:
Hi Matt,
I can try to write
> the test_string tests in Ruby 1.9 repository do seem to mostly function
You mean test/ruby/test_m17n.rb, test/ruby/test_m17n_comb.rb,
test/ruby/test_io_m17n.rb and test/ruby/enc/test_*.rb?
test/ruby/test_string.rb does not contain anything m17n related.
> We simply could not match Ruby regex exa
Hi Matt,
I can try to write something. Yesterday, I began to read the source
code of the main examples from the macruby package.
During this week, I will continue to read and understand HotCocoa and
after that, I should make a proposal on the mailing list.
Tell me if you are interested,
Vincent Isambart wrote:
I think everyone agrees that having a Ruby 1.9 String specs will be
necessity. And we'll also need to decide what parts of it to follow
and what parts we do not need to. For example handling access to
characters in a string with a partly invalid encoding exactly the same
w
> That's actually wrong. All force_encoding does is change the encoding
> attribute of the string, it shouldn't change the internal encoding of the
> bytes. The encoding attribute is basically a switch to describe which set of
> string methods should be used on the bytes.
That's what force_encodin
On Apr 8, 2009, at 7:23 AM, Benjamin Stiglitz wrote:
When doing force_encoding, convert to a ByteString in the old
encoding, then try to convert to an NSString in the new encoding. If
we succeed, great. If not, leave as a tagged ByteString (and
probably whine about it).
That's actually w
16 matches
Mail list logo
