Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

wxPerl Object Store

by jmlynesjr (Deacon)
on Nov 09, 2014 at 00:20 UTC ( [id://1106590]=perlquestion: print w/replies, xml ) Need Help??

jmlynesjr has asked for the wisdom of the Perl Monks concerning the following question:

Greetings:

I'm currently playing with wxTreeCtrl and I'm at the point of wanting to be able to save and retrieve the Tree. I've looked at Storable and have tried    my $info = Storable::nstore($self->{TREE}, $path).A file is being created, but only contains 25 bytes.

Anyone have any ideas on doing this? In the mean time, I'm looking at stringifying the Tree and storing it myself.

Crossposted to wx-Users mail list.

James

There's never enough time to do it right, but always enough time to do it over...

Replies are listed 'Best First'.
Re: wxPerl Object Store (nothing for sale)
by Anonymous Monk on Nov 09, 2014 at 00:43 UTC

      Thanks for the references. I need to reread Storable in more detail. I'm familier with the wxTreeCtrl methods which I will need to use to roll my own Store. I'm working on that now. I was hoping someone had already solved this problem. But, it will be a good learning experience anyway.

      James

      There's never enough time to do it right, but always enough time to do it over...

Re: wxPerl Object Store
by boftx (Deacon) on Nov 09, 2014 at 00:25 UTC

    Show us some code, for starters.

    As an aside, I couldn't help but notice the quote in the OP: "There's never enough time to do it right, but always enough time to do it over..."

    Why does it seem that all too many proponents of Agile think that is an acceptable way to do things?!?

    You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

      The quote comes from years of working in a small technical area within a giant non-technical company. This company would announce fixed opening dates four years in advance, then allow physical construction to eat up all the slack time allocated for systems installation and integration while constantly changing specifications. Besides months of 16 hour days, 7 days a week by the software group, several very public failures resulted in adding back months to the schedule and adding millions back to the budget. Management never listened until the missed opening made their sponsors look bad to the public. Thus arose one of our favorite sayings.

      James

      There's never enough time to do it right, but always enough time to do it over...

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://1106590]
Approved by GrandFather
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (8)
As of 2024-04-19 15:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found