Gateway
BOT
16-Apr-19 01:20 PM
[dscrd-hush] <tedy> Unfortunatelly I have already deleted old blockchain so can't verify the data directly so I'm relying on this block explorer
[dscrd-hush] <tedy> could be wrong
[dscrd-hush] <dukeleto> @tedy add up every unspent 12.5 utxo on the explorer page, it adds up to less than 262 i think. I did it manually
[dscrd-hush] <dukeleto> you would need ~21 block rewards to have 262 HUSH
[dscrd-hush] <tedy> Yes, and there are exactly 21 utxo's..
[dscrd-hush] <dukeleto> and i think i do see 21 BR's there
[dscrd-hush] <dukeleto> yes, agreed
[dscrd-hush] <ComputerGenie - ChickenPool> 2019-04-16 13:23:46 Still rescanning. At block 85648. Progress=0.210061...
2019-04-16 13:26:46 Still rescanning. At block 312401. Progress=0.752608...
(edited)
[dscrd-hush] <tedy> And 9 of them will be airdroped, but 12 of them not (I'm guessing those were immature blocks at snapshot)
[dscrd-hush] <tedy> It's just a guess, I don't know exactly why the difference..
[dscrd-hush] <dukeleto> it takes 100 blocks to be mature, is one thing. So if this is really a bug, all block rewards <100 confirms would not be in snapshot, but that doesn't seem to be happening either
[dscrd-hush] <tedy> That's correct.. it doesn't add up, therefore I have no idea what caused the difference
[dscrd-hush] <JWolf (WW Clan leader)> so what happens to the blocks on the old chain after the snatshot? If this test drop value is correct Ill be missing about 140...
[dscrd-hush] <ComputerGenie - ChickenPool> so what happens to the blocks on the old chain after the snatshot?
they exist forever
[dscrd-hush] <ComputerGenie - ChickenPool> unsupported
[dscrd-hush] <dukeleto> @JWolf (WW Clan leader) you are seeing some issue with immature block rewards as well?
[dscrd-hush] <dukeleto> I need to know how many block rewards you think are missing, and which blocks, would help, if known
[dscrd-hush] <JWolf (WW Clan leader)> wow but they are still mining the old chain on zhash...yeah 1sec
[dscrd-hush] <dukeleto> @JWolf (WW Clan leader) Zcash world believes in forcibly turning off nodes that don't update
[dscrd-hush] <tedy> @JWolf (WW Clan leader) you were making transactions after the block 500000 so that's harder to investigate
[dscrd-hush] <dukeleto> Hush does not believe that, we give people freedom and financial freedom to do what they think is best
[dscrd-hush] <dukeleto> @tedy how much, in total, do you think your snapshot value is off?
[dscrd-hush] <dukeleto> @JWolf (WW Clan leader) how much do you believe you are off, in total?
[dscrd-hush] <tedy> @dukeleto exactly 12 blocks<PHONE_NUMBER>7 HUSH difference)
(edited)
[dscrd-hush] <JWolf (WW Clan leader)> 35.43389105
[dscrd-hush] <JWolf (WW Clan leader)> lol mybad thought is was more
[dscrd-hush] <TryFingerButHole> scandalous
[dscrd-hush] <ComputerGenie - ChickenPool> @dukeleto as far as I can tell, @tedy is correct
on the old chain he has 21 UTXOs that are all generated:true, all before the 500k mark, and 12 of them are not included in the airdrop
[dscrd-hush] <JWolf (WW Clan leader)> Still all the hash being spent on the old chain at zhash boggles boggles my mind. why are they still running it?
[dscrd-hush] <ComputerGenie - ChickenPool> why are people mining ETC?
[dscrd-hush] <TryFingerButHole> why are people?
[dscrd-hush] <dukeleto> Why Finger But Hole?
[dscrd-hush] <JWolf (WW Clan leader)>
[dscrd-hush] <JWolf (WW Clan leader)> try a thumb
[dscrd-hush] <ComputerGenie - ChickenPool> Why Finger But Hole?
I'm told some folks like it
[dscrd-hush] <dukeleto> I am very willing to entertain the idea that there is a very deep bug, and nobody has ever noticed. This is really an edge-casey thing. I think mature coinbase should be included, but the internals of getsnapshot, lets just say it's a special kind of sausage factory
[dscrd-hush] <dukeleto> @JWolf (WW Clan leader) @tedy if you both send me a DM with "This address should have X but because of immature coinbase seems to only have Y", I will make sure to send y'all some extra after the snapshot. As far as I can tell, you are right. Fixing getsnapshot or changing the airdrop data is not really feasible, it's the closest thing to "correct" we have.
[dscrd-hush] <dukeleto> does that seem fair to everybody?
[dscrd-hush] <dukeleto> No UTXOs Left Behind
[dscrd-hush] <JWolf (WW Clan leader)> yeah 4sure its not even 1% thanx man
[dscrd-hush] <dukeleto> coolsies
[dscrd-hush] <TryFingerButHole> tis' a dark souls reference. you had a whitelist of terms you could use for messages in multiplayer
[dscrd-hush] <TryFingerButHole> people got creative
[dscrd-hush] <dukeleto> @ComputerGenie - ChickenPool do you see any weirdness on your addresses?
[dscrd-hush] <dukeleto> I am wondering how many miners have immature coinbase issue, I guess it's only miners that mined the last 100 blocks
[dscrd-hush] <ComputerGenie - ChickenPool> his was easier to check I haven't gotten to mine yet
[dscrd-hush] <tedy> @dukeleto Sure buddy, as I said I could live without that also, just mentioned it since I've noticed the difference and been wondering if there's more to that
[dscrd-hush] <JWolf (WW Clan leader)> probably everyone thats still mining the old chain
[dscrd-hush] <tedy> The other (non-mining utxo's) are the same so it's all good
[dscrd-hush] <ComputerGenie - ChickenPool> but tedy's is definitely off
$ ./hush-cli listunspent 0 999999 "[\"t1LF2cQhSbT8XiuSuYDzsvRoXicEYnNqUbL\"]" | jq '[ .[] | select(.confirmations > 1000) ] | length'
21
(edited)
[dscrd-hush] <dukeleto> since it's only the last 100 blocks, I think the max difference the airdrop would be off is 1250 HUSH, if there is an immaturity bug in getsnapshot
[dscrd-hush] <dukeleto> I trust getsnapshot a lot for normal UTXOs, but I can imagine there is a bug with immature stuff
[dscrd-hush] <penguin> There are times also that i've seen, when the pool takes longer for the block to confirm (100+), therefore delaying payout - so it could be a bit more?
(edited)
[dscrd-hush] <ComputerGenie - ChickenPool> payout would be a different matter, the pool would still have it in a correct snapshot
[dscrd-hush] <penguin> ohkk, but it wouldn't have been paid out to the miner address ?
[dscrd-hush] <dukeleto> @tedy you gonna get an extra tip/bounty for bringing this bug to light, nice work , and @JWolf (WW Clan leader) thanks for confirming
[dscrd-hush] <JWolf (WW Clan leader)> awesome, thanx
[dscrd-hush] <JWolf (WW Clan leader)> I was just talking to zhash too should be shutting there old pool down soon lol
[dscrd-hush] <JWolf (WW Clan leader)> the less angry miners the better....
[dscrd-hush] <dukeleto> yeah, since Zhash supports new hush, not sure why they didn't shut down the old one yet
[dscrd-hush] <dukeleto> But I am not a pool op
[dscrd-hush] <JWolf (WW Clan leader)> they're still spending 650ksols on the old chain lmao
(edited)
[dscrd-hush] <dukeleto> just a lowly dev
[dscrd-hush] <ComputerGenie - ChickenPool> @dukeleto mine does indeed seem to be off by 2 blocks
[dscrd-hush] <dukeleto> @ComputerGenie - ChickenPool since James had to ask me to help finish getsnapshot because the internals are so crazy, I can very much believe this
[dscrd-hush] <ComputerGenie - ChickenPool> the part that confuses me is why his would be off by more
[dscrd-hush] <dukeleto> i think the bug is subtle, maybe to do with internal locks
[dscrd-hush] <dukeleto> it's not "all immature coinbase are ignored", that would be too simple
[dscrd-hush] <dukeleto> it's most likely the last few blocks of coinbase
[dscrd-hush] <dukeleto> oh, wait
[dscrd-hush] <dukeleto> there are concepts that only exist in the internals, and life gets really complex
[dscrd-hush] <dukeleto> there is an idea of a "finalized" transaction, that could be coming into play. I want to understand this bug for the future, but it's not critical righ tnow
[dscrd-hush] <JWolf (WW Clan leader)> the old chain Network Difficulty : 44.55 M
[dscrd-hush] <JWolf (WW Clan leader)> still double
[dscrd-hush] <ComputerGenie - ChickenPool> @dukeleto anything else you'd like me to check before I close legacy back down?


Source code for pyproct.protocol.saveTools
'''
Created on 20/09/2012
@author: victor
'''
import shutil
import pyproct.tools.pdbTools as pdb_tools
import os.path
from pyproct.driver.handlers.trajectoryHandler import TrajectoryHandler
from pyproct.tools.pdbTools import get_model_boundaries,\
repair_MODEL_ENDMDL_tags
#TODO: do_merged_files_have_correlative_models seems to be unnecessary
[docs]def merge_pdbs(trajectories, temporary_merged_trajectory_path, do_merged_files_have_correlative_models = True):
pdbs = []
if trajectories.__class__ == TrajectoryHandler:
pdbs = [pdb["source"] for pdb in trajectories.pdbs]
else:
pdbs.extend(trajectories)
# Copy the first one (there's at least one)
shutil.copyfile(pdbs[0], temporary_merged_trajectory_path)
file_handler_out = open(temporary_merged_trajectory_path, "a")
for pdb_file in pdbs[1:]:
# Concat the other files
file_handler_out.write(open(pdb_file,"r").read())
file_handler_out.close()
if do_merged_files_have_correlative_models: # if true merged file changes its frame numbers
shutil.copyfile(temporary_merged_trajectory_path,
temporary_merged_trajectory_path+".mdl")
file_handler_in = open(temporary_merged_trajectory_path+".mdl", "r")
file_handler_out = open(temporary_merged_trajectory_path,"w")
current_model = 0
for line in file_handler_in:
if line[0:5] == "MODEL":
file_handler_out.write("MODEL "+str(current_model).rjust(8)+"\n")
current_model = current_model + 1
else:
file_handler_out.write(line)
file_handler_out.close()
file_handler_in.close()
[docs]def save_representatives(representatives,
pdb_name,
workspace_handler,
trajectory_holder,
do_merged_files_have_correlative_models,
write_frame_number_instead_of_correlative_model_number,
keep_remarks = False):
"""
Saves a pdb file containing the most representative elements of the clustering.
@param representatives: A list of the representative elements of the clustering we want to extract.
@param workspace_handler: The workspace handler of this run.
@param trajectory_holder: The trajectory handler for this run or an array with pdb file paths.
@param do_merged_files_have_correlative_models: When merging, output file will have models from 0 to M, where M is the total number
of frames of the merged file.
@param write_frame_number_instead_of_model_number: When extracting frames, extract those models which number coincides with the
frame numbers in 'representatives'. Otherwise, extract those models which position coincide with the frame number in
'representatives'.
"""
results_directory = workspace_handler["results"]
# Merge pdbs (in order)
temporary_merged_trajectory_path = os.path.join(workspace_handler["tmp"],"tmp_merged_trajectory.pdb")
merge_pdbs(trajectory_holder,
temporary_merged_trajectory_path,
do_merged_files_have_correlative_models)
# Extract frames from the merged pdb
file_handler_in = open(temporary_merged_trajectory_path,"r")
file_handler_out = open(os.path.join(results_directory,"%s.pdb"%pdb_name),"w")
pdb_tools.extract_frames_from_trajectory_sequentially (file_handler_in = file_handler_in,
number_of_frames = pdb_tools.get_number_of_frames(temporary_merged_trajectory_path),
file_handler_out = file_handler_out,
frames_to_save = representatives,
write_frame_number_instead_of_correlative_model_number = write_frame_number_instead_of_correlative_model_number,
keep_header = keep_remarks)
file_handler_in.close()
file_handler_out.close()
return os.path.join(results_directory,"%s.pdb"%pdb_name)


Gridfolio
2.0
A minimalistic library to generate grid-based portfolios. Simple, slick, responsive, and easily customizable.
$ git clone https://github.com/christinecha/gridfolio
documentation
Preview Built-in Themes (more coming soon)
classic
warhol
circular
brutalist


Seer Tanapi:
I have sent word that you are coming to see the
Flame Lord
! You must not keep him waiting! Hurry!


Credits
Idea and development -
Denis Zavershinskiy
Design - anonymous designer
Logo - anonymous designer
You can find source code in
Github


RESONO holds within its management team over 16 years experience working in the BPO low-cost operating environment, serving Australian clients seeking to maximise their revenues by off-shoring projects to South-East Asia.
Chris Page | President
Born in Christchurch, and having worked in New Zealand, Australia, Malaysia, Japan, the UK, now based in Manila, Chris brings to RESONO 8 years of experience working in the BPO industry, managing transition projects for large Australian companies to offshore suppliers in Asia. Chris will ensure your commercial returns are maximised by managing the development of end-to-end processes to generate the best returns from your RESONO BPO solution.
Kee-Hui Wang | Director of Operations
Kee-Hui's extensive knowledge of BPO operations models started 8 years ago when he was working in the financial industry in Kuala Lumpur. During the rapid expansion of the BPO industry in Malaysia in the mid-2000’s,Kee-Hui successfully managed several expansion projects for Australian clients into South-East Asia.


People who make computer systems including a User Interface (UI) often refer to the Model View Controller (MVC) pattern to drive their design. MVC is actually a mainstream pattern of fundamental importance. But there are lots of misunderstandings about MVC and some improved patterns have been proposed to address some problems of the original MVC, which by the way is rather old.
The basic good idea behind MVC - and it was MVC to first introduce it - is Separated Presentation, as defined by Martin Fowler (emphasis is mine):
Ensure that any code that manipulates presentation only manipulates presentation, pushing all domain and data source logic into clearly separated areas of the program. ... The idea behind Separated Presentation is to make a clear division between domain objects that model our perception of the real world, and presentation objects that are the GUI elements we see on the screen. Domain objects should be completely self contained and work without reference to the presentation, they should also be able to support multiple presentations, possibly simultaneously.
This is basically a refinement of Separation of Concerns (SoC) for the UI context. The structure of MVC is the following:
20120808/MVC-class-diagram.png
There are three participants in the pattern:
Person
objects). It might be connected to a persistence
facility (e.g. a relational database) and allow concurrent modification by means of transactions, but this is
not relevant in the MVC perspective; actually the Model can be designed in many different ways. What's important
is that it contains domain objects and exposes functions to manipulate them. This participant is completely
ignorant of the UI - it even doesn't know what a UI is.From a dynamic point of view the interactions in a MVC design can be modelled as the union of two Observer patterns. Fowler calls it Observer Synchronization:
20120808/MVC-sequence-diagram.png
Since design patterns in the real world are seldom found in a “pure“ way, there can be many legitimate variations
on the basic theme. On the other hand MVC is probably one of the most misused terms in computer engineering: many
people use the term just to mean Separated Presentation, that is a “good” design of a UI, but they aren't actually
using MVC.
Before going on and criticize MVC, it's fundamental to understand a few points:
javax.swing.table.TableModel
,
Android android.widget.Adapter
and Vaadin com.vaadin.data.Container
.
These are adapters that “translate” data in a way that can be directly consumed by the UI components. This
concept, which is pretty useful, is called “Presenter” by a variation of MVC called Model
View Presenter (MVP). For the scope of this discussion, we consider that the characterizing feature of MVC is the direct communication between the Model and the View, which is the source of many issues. Let's ask ourselves some questions:
The most valuable parts of the design are the Model and the Controller. The former is part of the Domain Model,
which is the core of our project, and it has got a strict relationship with data and business rules, which usually
are the most stable and valuable portions of a software application. The latter implements the presentation logic
and it's responsible for doing the right things on behalf of the user itself.
The least valuable part of the design should be the View. UI technologies are very volatile (I'd also say
fashionable) and very depending on the context. If we don't have specific deployment issues (it happens for
instance where deployment is supervised in some way) we can realize a full fledged desktop application by using
Swing, JavaFX 2, the NetBeans or the Eclipse Platforms. If we have deployment issues it's better to go with a web
application, for instance made with Vaadin. If we want to run on mobile appliances, we could pick Android.
Why am I mentioning Vaadin as a web technology example? For this blog post I'm keeping quite generic about UI
technologies, just stressing the fact that I want a design that doesn't depend on them. But in practice I know
that it works with the class of UI technologies that support “push updates”, that is UI
changes that are performed in reaction to a stimulus originating from the server. Most of the technologies that
are not web based support them, but the traditional web frameworks don't since they restrain updates within the
“pull” approach typical of a HTTP request/response. Fortunately, modern frameworks for Rich Internet
Applications support push updates by means of AJAX. Vaadin is one of them; it's not the only one, but one that I
have a good experience of.
All these technologies have their own libraries for creating a UI, so an hypothetical application that must be
deployed to multiple channels (e.g. Web and Android), or that during its life must be ported from an environment
to the other, should be able to change its View implementation with the minimal effort and without touching the
Model and the Controller.
Unfortunately, MVC doesn't separate enough for accomplishing to this requirement. These are some of the most common issues (in random order):
java.util.Date
, but almost for sure we want it to be rendered in
a human readable way, often localized. This behaviour wouldn't change whether we have a desktop, a web or a
mobile application, so if it is implemented in the View we are going to lose it when that specific View
implementation goes away - and re-implement it in the new View.TemperatureWidget
, but since
widgets are technology dependent this ends up in making a SwingTemperatureWidget
, a VaadinTemperatureWidget
and an AndroidTemperatureWidget
. This ends up with further presentation logic in the View
implementation that will be lost when that implementation goes away.For what concerns testing, there's an additional point. Even if you ignore the problem of switching the UI technology, automatic testing of a UI can be complex. There are many products that allow to do things such as recording user gestures, playing them back against a UI and asserting postconditions (Selenium being one of the popular ones in the web world), but after some initial enthusiasm I find that they are too much expensive to use and to maintain. I had a better experience with Swing automated testing, but now I think that a cheaper, alternate way of testing a UI must be found.
The underlying issues that we can infer from the previous points is that in MVC:
What we really need is a dumb View, really focused only on the graphic responsibilities. This is where Presentation Abstraction Control (PAC) can help.
We can see PAC as an evolution of MVC: we still have three participants, but responsibilities are better distributed in two of them and there's some clean up in the interactions:
20120808/PAC-class-diagram.png
The different responsibilities of the pair PC with respect to VC are clear if you look at the interactions in the diagram:
20120808/PAC-sequence-diagram.png
A good general guideline for evaluating a design is the presence or lack of symmetry. Generally speaking, symmetry is a plus. An asymmetry means that one task and its opposite, or its complementary, are performed in a different way. Unless there's a specific reason, this is just unjustified complexity, to be eliminated to comply with the Occam's razor. Compare the sequence diagrams for MVC and PAC: while PAC is symmetric (both interactions originating from the View and from the Abstraction linearly involve all the three participants), MVC is not (interactions originating from the Model don't involve the Controller).
There's no coupling between the Presentation and the Abstraction, as everything is mediated by
the Control. In this way, the Control can take care of all the presentation logic and there are no residual parts
in the Presentation. Referring to one of the examples above, when we need to render a Date
, this
means that it's possible to format it in the Control and then pass a String
to the Presentation. In
other words, this means that, when speaking of simple data items, the Presentation can only deal with String
s,
to be rendered as they are. For instance, look at this code sketch:
public interface PersonAbstraction
{
public Date getBirthDate();
}
public interface PersonPresentation
{
public void renderBirthDate (String birthDate);
}
public class PersonControl
{
private PersonAbstraction person = ...;
public void populateBirthDate()
{
SimpleDateFormat format = new SimpleDateFormat(...);
presentation.renderBirthDate(format.format(person.getBirthDate()));
}
}
public class SwingPersonPresentation extends JPanel implements PersonPresentation
{
private JTextField tfBirthDate = new JTextField();
public void renderBirthDate (String birthDate)
{
tfBirthDate.setText(birthDate);
}
}
As promised, no logics in the Presentation. Just get incoming data and render them in the proper place. All the
other mentioned problems can be solved in a similar way: for instance, decide which colour to use in the Control
and then call Presentation methods such as renderTemperature (int value, Color color)
. Imagine that
an implementation for Vaadin or Android wouldn't be much different.
In the original description of PAC there's much more than this. For instance the pattern is defined in terms of agents and in general there's a better guidance to decomposing complex UIs. All interesting stuff that I'm ignoring in the scope of this post, but that I will pick in future.
 The whole
set of user-UI interactions now stays in the Control, so it can be tested by mocking both the Presentation
and the Abstraction with one of your regular Java tools such as JUnit, TestNG and Mockito. It also means that you
can design in TDD (Test Driven Design) if you wish. More
sophisticated testing can include integration tests where you have almost the whole application (I mean, the
Abstraction is the real back end, not mocked), while the Presentation is still mocked.
There are some things to be clarified here. With this simplified kind of tests are you safe that Presentation
is populated with the correct data and the application properly reacts to user gestures? Not completely. What
you're sure of is that the object implementing the Presentation is called with the correct data and that when
the callbacks in the Control are invoked the proper behaviour is triggered. What you miss is the very last step
("the last mile"): your specific Presentation implementation could miss to pass an inbound string to JTextField.setText()
or could forget to bind a JButton
to the Control callbacks. So, by restricting automated tests to
mocked Presentations you're losing something. Is this a problem? How can be solved? Consider the following
points:
setText()
), or they are correct (because they have
been prepared by the Control). In a similar fashion, in a View pressing a button could trigger the wrong
behaviour; with a Presentation either the button does nothing or it does the right thing (because it's fully
implemented by the Control). Of course “less probable” doesn't mean ”impossible”: but given that you have to
perform some human-based testing anyway, the human tester can also easily spot the trivial errors that we are
talking about. The added cost of to perform this task is negligible. The details about testing will be more clear when I'll introduce some real-world code in a further post.
Summing up, PAC solved some problems, with the exception of two: the UI behaviour consistency and the lack of flexibility of the data binding. That's what the Presentation Model is for.
Martin Fowler defines the Presentation Model as (emphasis is mine):
Represent the state and behavior of the presentation independently of the GUI controls used in the interface. ... Presentation Model pulls the state and behavior of the view out into a model class that is part of the presentation. The Presentation Model coordinates with the domain layer and provides an interface to the view that minimizes decision making in the view. The view either stores all its state in the Presentation Model or synchonizes its state with Presentation Model frequently. ... A view then simply projects the state of the presentation model onto the glass.
In other words, the Presentation Model is a sort of intermediate object between the Presentation and the
Abstraction. It doesn't have any knowledge of specific UI widgets, but provides the models that can be bound to
them. For instance, an Abstraction can represent a Person
in a registry with the name, the job
description and a photo. Its Presentation Model could provide a short description (e.g. name + job) to be rendered
in a list row, transform the photo into a small icon to be rendered near the description, and provide callbacks
for the click and double click gestures, as well as an enumeration of further callbacks that could be rendered in
a contextual menu.
The Presentation Model is a very similar concept to the Presenter in the previously cited Model View Presenter pattern.
It's a responsibility of the Control to instantiate and properly prepare a Presentation Model for an Abstraction.
The Control would never directly expose an Abstraction to the Presentation to ask for it to be rendered; in its
place it would pass the Presentation Model for it. In other words, we can say that the Presentation would never
see and access a “naked” Abstraction, but only operate on it by means of its Presentation Model. Thus, the
Presentation Model works as an Adapter of the
Abstraction for the Presentation. By creating the same Presentation Model for a given Abstraction and reusing it
for all the PAC instances in our application we are making sure that the UI will always behave in a consistent
way.
The Presentation Model can also provide a solution for flexible data binding: instead of binding the Presentation to the Abstraction, you can bind it to the Presentation Model. It can expose a mix of the original Abstraction properties and derived ones (such as the description defined as name + job in the previous example).
20120808/PAC-with-PM-class-diagram.png
Generically speaking, the Presentation Model shouldn't depend on any UI technology. For instance, a developer
focusing on Swing could be tempted to model the callbacks for the click gesture as a javax.swing.Action
:
after all, a Swing Presentation could easily pull it out of the Presentation Model and register it to a Swing
component. In a similar fashion, if the Abstraction contains a hierarchic data structure that can be rendered, one
might be tempted to implement it with a javax.swing.tree.TreeModel
in the Presentation Model.
Unfortunately, this would make the Presentation Model unusable with Vaadin or Android. Thus, the PresentationModel
should expose generic classes (e.g. generically designed things such as CallBack
or Hierarchy
).
These generic classes would be then “adapted” to their Swing, or Vaadin, or Android counterparts. This sounds as
an additional work, but it's very simple and reusable, as shown by the following diagram:
20120808/Real-world-PM-class-diagram.png
Entities outside the packages are not depending on any UI technology; entities in the “Swing & reusable ..." package are reusable for all applications based on the Swing technology. Similar diagrams for Vaadin or Android could be drawn by just replacing the specific classes.
Sometimes it's advisable the opposite approach because some UI technology could already provide existing classes
that are already a good Presentation Model or a good basis for it. The NetBeans Platform, for instance, offers a org.openide.node.Node
class which is an excellent support, performing a number of integration tasks with the rest of the Platform. It
could be expensive to rewrite that features. With the NetBeans Platform my approach is to use a Presentation Model
implementation that inherits from Node. Both approaches can be made to co-exist by referring to a Presentation
Model by means of an interface (or abstract class) and using a Factory
pattern which returns the most appropriate implementation.
There's a trade off to apply here and often you have to give up to something. Most UI frameworks, or add-on
libraries for them, offer specific support for common tasks: for instance, think of a table model that is
associated to a SQL query, capable of self-populating and perhaps even in lazy mode (by just querying the
minimum set of data to fill the page). In other cases, such as in Vaadin, you have specific APIs for building an
Abstraction upon them. By using those features the UI framework will let you create a working application in
minutes - a faster approach, definitely. My take is that you should give up to that (unless you are just doing a
quick prototype): what you gain in the short term will show an additional cost in the medium and long term. My
experience is that with the proper design it's not hard to develop a small set of classes that offer the same
features in a UI technology neutral fashion. Of course, only you can make the correct evaluation, case by case.
PAC and Presentation Model, when properly implemented, can solve all the MVC issues that we've mentioned. But we can further improve our design to add some flexibility. For instance, for what concerns UI consistency, we assumed that a given Abstraction must be rendered always in the very same way throughout the UI. But sometimes there are exceptions: for instance, in some cases we'd like to prevent a contextual menu from appearing, in other cases we'd like to add or remove some menu item. Or we could need slightly different behaviours of the same PAC reused in two different applications. The most immediate solution is to implement alternate Presentation Models. But there's a better approach that delivers this flexibility without a proliferation of Presentation Models - indeed, we could even have only one single Presentation Model for everything!
Data Context and Interaction (DCI) is the pattern that can help us. First, let's recall its basic concepts. This pattern is made of three participants:
BankAccount
example, there would not be a transfer()
method (this requires another BankAccount
,
or another source or target), but a withdraw()
or a deposit()
(that is, the
“partial” operations that are seen by a single instance of Datum). Apart from this refinement, a Datum is very
close to the Model in MVC and to the Abstraction in PAC.Transferable
role can expose the transfer()
method by making bankAccount1.withdraw()
and bankAccount2.deposit()
to properly cooperate. Roles are stateless since they always operate on the state provided by a Datum (by means
of methods exposed by Datum, or perhaps by directly accessing its state - it's reasonable to think of a Role as
a friend class to a Datum). Transferable
can be applied to a
BankAccount
, but also to a CashAmount
, or a DebitCardAccount
and such.BankAccount implements Transferable
, but rather a
getTransferable()
method in BankAccount
(or something even better).20120808/DCI-class-diagram.png
Given these premises, we can infer the following facts:
Renderable
, Clickable
, ContextualMenuProvider
.The fact that there are classes that are never seen “naked”, but accessed by means of adapters, should remind you
of something I've written in the previous paragraph about the Presentation Model. Actually, we can think that if
we're able to provide a set of UI-related Roles, properly designed so they are not technology-dependent, we can
integrate PAC, Presentation Model and DCI so the Presentation Model just becomes a container of DCI Roles.
In this perspective, the PAC Control is also a DCI Context which, knowing both the DCI Datum and the PAC
Presentation, creates a Presentation Model with the Roles required for the interaction with the UI. Being the new
Presentation Model just a dynamic container of Roles, it's possible to think of a universal Presentation
Model for any kind of Abstraction.
Note that the Abstraction itself can be designed according to DCI (i.e. it could be already an aggregate of a
Datum and Roles) or not. In the latter case, the Control would always create the Roles from scratch; in the
former case, it could reuse some existing Role already present in the Domain Abstraction. I think that there are
advantages in using DCI also for the Abstractions an application, but this is not a requirement. In
other words, if you already have a back-end design not made with DCI, you can safely introduce DCI only for the
Presentation and Control.
The dynamic and flexible behaviour in the presentation logic we were advocating for can be now easily achieved
with the proper design. Instead of having hardwired methods such as:
public interface PresentationModel
{
public Clickable getClickable();
public ContextualMenuProvider getContextualMenuProvider();
}
we can think of something generic such as:
public interface PresentationModel
{
public <Role> Role as (Class<Role> roleType);
}
So we can think of a Presentation containing the following code:
PresentationModel pm = ...;
pm.as(Clickable.class).click();
pm.as(ContextualMenuProvider.class).renderContextualMenu();
This Presentation Model would allow to dynamically add, remove or replace Roles according to the needs of the specific Context, furthermore without having to rely on a closed set of predefined Roles.
I've been using these patterns together with success for a few years now in various projects using Swing + NetBeans Platform, Vaadin and Android. In this post I've kept code samples at a minimum in order to focus more on concepts and UML diagrams. Full examples of working Java code will be the focus of further posts.


--- layout: page title: About header-img: "img/about-bg.png" ---
Software Engineering student at FlatIron School part-time around being a banker and single mother.


geocircle QML Basic Type
The geocircle type represents a circular geographic area.
The geocircle
type is a geoshape that represents a circular geographic area. It is a direct representation of a QGeoCircle and is defined in terms of a coordinate which specifies the center of the circle and a qreal which specifies the radius of the circle in meters.
The circle is considered invalid if the center coordinate is invalid or if the radius is less than zero.
Example Usage
Use properties of type variant to store a geocircle
. To create a geocircle
value, use the QtPositioning.circle() function:
import QtPositioning 5.2 Item { property variant region: QtPositioning.circle(QtPositioning.coordinate(-27.5, 153.1), 1000) }
When integrating with C++, note that any QGeoCircle value passed into QML from C++ is automatically converted into a geocircle
value, and vise-versa.
Properties
center
coordinate radius
This property holds the coordinate of the center of the geocircle.
radius
real radius
This property holds the radius of the geocircle in meters.
The default value for the radius is -1 indicating an invalid geocircle area.


Bob the Happy Bastard's Quickie Review:
THE ODD COUPLE II
Grumpy Old Men, it ain't. Hell, My Fellow Americans, it ain't.
Walter Matthau and Jack Lemmon team up again for an even more worn out vehicle than any of their films over the past few years. Odd Couple II feels terribly generic, where in the first movie, made thirty one years ago, feels like a wonderful tale. That's like repackaging Campbell's Soup in a generic food can, really.
How writer Neil Simon could've made such a horrible mistake in screen writing is beyond me. Throughout the movie, I really didn't laugh once. Honestly. I mean, there were dumb situations, yeah, like the cropduster who let these old geezers have it without any notice, but they just really didn't seem funny to me. And that car rolling off the cliff? The only way I would've seen humor in that is if they were still in it.
And the ending gets all super-mushy, too. In the final twenty minutes or so, Lemmon meets a girl he thinks is the one, then loses her; Matthau talks to his son (a wasted Jonathan Silverman) about his amrriage to Lemmon's daughter; and, of course, Lemmon and Matthau have another roomie situation on their hands. Ooh, I really gave a lot away there, I'm sure.
RATING: 1 (out of 10)
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


EBD - Easton Bible DIctionary
Tackling
TACKLING
"TACKLING "(
Isaiah 33:23
), the ropes attached to the mast of a ship. In
Acts 27:19
this word means generally the furniture of the ship or the“gear” (
27:17
), all that could be removed from the ship.
"TACKLING "(Isaiah 33:23), the ropes attached to the mast of a ship. In Acts 27:19 this word means generally the furniture of the ship or the“gear” (27:17), all that could be removed from the ship.


Everyone tells me how good pizza but as I am a vegan i decided to make an alternative so that i too could try it.
PIZZA
1/2 of one Trader Joe’s garlic-herb pizza crust (or half of this homemade recipe or this gluten-free recipe)
1/2 cup each red, green, and orange bell pepper (loosely chopped)
1/3 cup red onion (chopped)
1 cup button mushrooms (chopped)
1/2 tsp each dried or fresh basil, oregano, and garlic powder
1/4 tsp sea salt
SAUCE
1 15-ounce can tomato sauce* (organic when possible)
1/2 tsp each dried or fresh basil, oregano, garlic powder, granulated sugar
~1/4 tsp sea salt (to taste)
TOPPINGS
1/2 cup vegan parmesan cheese
Red pepper flake + dried oregano
Instructions
Preheat oven to 425 degrees F (218 C) and position a rack in the middle of the oven.
Bring large skillet to medium heat.
Once hot, add 1 Tbsp olive oil (amount as original recipe is written // adjust if altering batch size), onion and peppers. Season with salt, herbs and stir.
Cook until soft and slightly charred – 10-15 minutes, adding the mushrooms in the last few minutes. Set aside.
Prepare sauce by adding tomato sauce to a mixing bowl and adding seasonings and salt to taste. Adjust seasonings as needed. Set aside. Note: If using tomato paste, add water to thin until desired consistency is reached.
Prepare vegan parmesan if you haven’t already by blitzing raw cashews, sea salt, nutritional yeast and garlic powder in a food processor until a fine meal is reached. Transfer to jar and refrigerate to keep fresh.
Roll out dough onto a floured surface and transfer to a parchment-lined round baking sheet. You’re going to add the pizza WITH the parchment directly to the oven to properly crisp the crust, so any round object will do as it’s not actually going into the oven (I use a wood board).
Top with desired amount of tomato sauce (you’ll have leftovers, which you can store in a jar for later use), a sprinkle of parmesan cheese and the sautéed veggies.
Use the baking sheet to gently slide the pizza directly onto the oven rack WITH the parchment underneath. Otherwise it will fall through.
Bake for 17-20 minutes or until crisp and golden brown.
Serve with remaining parmesan cheese, dried oregano and red pepper flake. Leftovers keep well – no need to reheat! Cold pizza is yum.


The New England Colonists' English Image, 1550-1714
By David Hudson Corkran III
A.B. (Middlebury College) 1957 M.A. (University of California) 1960
DISSERTATION
Submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in History
in the GRADUATE DIVISION of the
UNIVERSITY OF CALIFORNIA, BERKELEY
Approved:
Degree conferred. DEGREE CONFER ED MAR CH 2, 1970 case
Date


Mobile Screenshot
Tablet Screenshot
Visible Page
Entire Page
Browser Mockup
Browser Mockup
Download Mockup


--- layout: article title: Getting to know Factories and Capybara date: 2015-04-08 15:25:54.000000000 -05:00 modified: categories: excerpt: tags: [] image: feature: teaser: rspec-teaser.jpg thumb: ---
It feels like forever since I was able to work on Rails applications without having to fix something with my computer or development environment but today ran incredibly smooth! It is quite the transition to go from troubleshooting hardware and operating system issues to developing software logic and web application flow. I love every second of it!
This morning I fully fleshed out my simple blog to practice RSpec, Capybara and Factory Girl. I created a repository for the testing blog on my GitHub account if you want to check it out. The goal for this project is to not only become familiar with the above programs but to educate myself about broader testing practices in general.
Factories
Factories allow you to define instances of an object for a testing environment in a flexible and adaptable manner. Factories generate their instances when called upon by a test, whereas fixtures are automatically loaded into the test database when testing begins. Fixtures skip the entire object creation process, meaning Active Record validations and callbacks do not work for them. Since factories are created using Active Record, they are required to pass through validations and callbacks and lend themselves to more complicated associations. Depending on the needs of your application, it is worth taking time to consider whether factories or fixtures would be a better fit.
Once the Factory Girl gem is installed, factories are defined in a /spec/factories folder. To define the post factory for my simple blog I wrote,
{% highlight ruby linenos %} FactoryGirl.define do factory :post do title "Post One" content "This is Post One" published false end end {% endhighlight %}This defines a factory, post, which I can use at any point when I am writing my RSpec or Capybara tests. Lets take a look at the spec I wrote for my post model and break it down
{% highlight ruby linenos %} require 'rails_helper' RSpec.describe Post, type: :model do it "has a valid factory" do expect(build(:post)).to be_valid end it "is invalid without a title" do expect(build(:post, title: nil)).to_not be_valid end it "is invalid without content" do expect(build(:post, content: nil)).to_not be_valid end it "is unpublished when created" do expect(build(:post).published).to eq(false) end end {% endhighlight %}The build method simply instantiates a new factory without saving it to the database. When the default build(:post) is run, it generates a post with the attributes we set in our factory definition. Since we need to generate a post that is invalid in the second assertion, it is simply a matter of calling build(:post, title: nil). This instantiates our default post but changes the title to nil. It really is just as easy as tacking on different options to fit each unique case.
Capybara
I had a bit of experience writing integration tests with the Rails Tutorial by Hartl before I began looking into Capybara. Capybara calls them 'feature' tests but they are just like integration tests in that they attempt to mimic the final user experience. With feature tests, the developer is primarily concerned with making sure the user sees what they should be seeing. It doesn't really matter how it all comes together behind the scenes -- let the model tests take care of that. If the user can move through the prescribed actions correctly and sees the correct views, then the feature test has done its job.
Below is the feature test mimicing how a user creates a post
{% highlight ruby linenos %} require 'rails_helper' feature 'User creates a new post' do scenario 'with valid attributes' do visit new_post_path fill_in 'post_title', with: 'My Title' fill_in 'post_content', with: 'Content' check 'post_published' click_on 'Create Post' expect(page).to have_content('Show Post') end scenario 'with invalid attributes' do visit new_post_path fill_in 'post_title', with: '' fill_in 'post_content', with: 'Content' check 'post_published' click_on 'Create Post' expect(page).to have_content('Create a Post') end end {% endhighlight %}Capybara uses 'feature' and 'scenario' much like RSpec uses 'describe' and 'context.' Capybara has methods that mimic user interaction with the browser like 'visit', 'fill_in' and 'check.' As you can see, the test reads very similar to standard English. For the scenario in which a user creates a post with valid attributes, the test first visits the page to create new posts. The test then fills in the title and content form fields with valid strings. The published checkbox is checked signifying the test wants the form to return true on the published attribute. By issuing "click_on 'Create Post,'" Capybara follows the controller commands dictating what to do when the submit button is pressed. Finally, the test finishes by making its first expectation, verifying the redirect contains the words "Show Post" somewhere on the page.
Now that I understand the basics behind each of these testing programs, it is just a matter of practice getting to know and understand the intricacies and exceptions.


|
Rover
1.0.0
school project
|
Inherits object.
Public Member Functions | |
| def | __init__ (self, pwmOut, directionOut, tcpCommunication) |
| def | run (self, dutyCycle) |
| def | setSpeed (self, dutyCycle) |
| def | speedUp (self, increment) |
| def | setDirection (self, direction) |
| def | getDutyCycle (self) |
| def | stop (self) |
| def | clean (self) |
Data Fields | |
| pwmOut | |
| directionOut | |
| tcpCommunication | |
| pwm | |
| pwmRunning | |
| currentDutyCycle | |
This class is used to control the motors of the Rover.
| def __init__ | ( | self, | |
| pwmOut, | |||
| directionOut, | |||
| tcpCommunication | |||
| ) |
This constructor initializes a new Motor object. :param pwmOut: The number of the pin that should be used as the output of the PWM :type pwmOut: int :param directionOut: A list that contains two numbers representing the pins that should be used to control the direction of the rotation. :type directionOut: list of ints
| def clean | ( | self | ) |
This method is called when the client disconnects. It stops the motors and cleans up the GPIO.
| def getDutyCycle | ( | self | ) |
:return: Value of current duty cycle :rtype: int
| def run | ( | self, | |
| dutyCycle | |||
| ) |
This method starts the PWM. It is pretty similar to the setSpeed() method. It either starts the PWM, if stopped, or only changes the duty cycle. :param dutyCycle: The duty cycle to be applied. 0 <= dutyCycle <= 100 :type dutyCycle: int :raises ValueError: A ValueError is raised when the argument <= 0 or 100 <= argument
| def setDirection | ( | self, | |
| direction | |||
| ) |
This method sets the rotation direction of the motor. :param direction: Direction to be applied. An enum *Direction* should be used. :type direction: boolean
| def setSpeed | ( | self, | |
| dutyCycle | |||
| ) |
This method sets the duty cycle of the PWM and thus changes the speed of the motor. It is pretty similar to the run() method but if the PWM is stopped,this method does not start it. :param dutyCycle: The duty cycle to be applied. 0 =< dutyCycle =< 100 :type dutyCycle: int :raises ValueError: A ValueError is raised when the argument <= 0 or 100 <= argument
| def speedUp | ( | self, | |
| increment | |||
| ) |
This methods sets a new speed by incrementing the current duty cycle by the given argument if possible. :param increment: The number that should be added to the current duty cycle :type increment: int :raises ValueError: A ValueError is raised when the (self.currentDutyCycle + increment) <= 0 or 100 <= (self.currentDutyCycle + increment)
| def stop | ( | self | ) |
This method stops the PWM.
| currentDutyCycle |
| directionOut |
| pwm |
| pwmOut |
| pwmRunning |
| tcpCommunication |


From the basics to the Puppet Forge, several ways to effectively manage configuration files with Puppet.
Working with files is one of the most common tasks when managing systems and therefore a routine task when working with a tool like Puppet. There are many to manage files with Puppet and last year I hosted a webinar about some of the options. I've been thinking a lot about them lately and thought others would find a written version useful.
For the purpose of comparison, all I'm looking to do is manage the configuration of /etc/ssh/sshd_config on a single Red Hat server. More Puppet code would be necessary to fully manage an ssh server and accommodate for multiple operating systems. Thankfully, the Puppet Forge offers plenty of options.
file { '/etc/ssh/sshd_config':
ensure => file,
mode => '0600',
owner => 'root',
group => 'root',
source => 'puppet:///modules/my_module/my_sshd_config',
}
This is the most blunt instrument you can wield with Puppet. We're instructing Puppet to take a file we have (the source line) and deliver that file to the machine we're managing with a particular mode, owner and group. Puppet will first compare checksums and if a change is needed, it will overwrite the file, reporting back a diff of what changed.
It's quick and easy but dirty. This technique forces everyone to manage that file through the same Puppet-sourced file (hope you're using version control) and every machine under management will get the same file, making it more complicated to account for differences between systems.
file { '/etc/ssh/sshd_config':
ensure => file,
mode => '0600',
owner => 'root',
group => 'root',
content => template('my_module/sshd_template.erb'),
}
Templates are much more practical. The documentation on Puppet templates will explain it in more detail but effectively, you're able to use information about the machine you're managing to tweak the configuration you actually manage on it. An example for sshd_config is the ListenAddress keyword. If we want it to be set to the ip address assigned to our machines eth0 adaptor, we simply need to specify the following in our sshd_config modeled as an erb template.
ListenAddress <%= @ipaddress_eth0 %>
Whenever Puppet runs on the machine you're managing, it delivers the value for ipaddress_eth0 (run facter ipaddress_eth0
to see it now) to the Puppet Master which builds the appropriate sshd_config file for the machine to manage, similarly to how static files are managed by Puppet. It's much more flexible but templating still expects you to manage the entire file with Puppet, using the same source file.
$file_to_manage = '/etc/ssh/sshd_config'
concat{ $file_to_manage:
owner => 'root',
group => 'root',
mode => '0600',
}
concat::fragment { 'Disclaimer':
ensure => present,
target => $file_to_manage,
order => '01',
content => "# This file is managed by Puppet - your edits will be overwritten\n",
}
concat::fragment { 'Listen':
ensure => present,
target => $file_to_manage,
order => '02',
content => "ListenAddress ${ipaddress_eth0}\n",
}
concat::fragment { 'Base':
ensure => present,
target => $file_to_manage,
order => '10',
source => 'puppet:///modules/my_module/sshd_config_base',
}
This pattern involves many more lines of Puppet code but it's infinitely more flexible than what you've seen so far. These concat resources come from the puppetlabs-concat module from the Puppet Forge. If you boil it down, it's an abstraction above static file serving and Puppet template creation. You tell Puppet that you care about individual fragments of a file which don't have to be defined in the same spot in your Puppet code. Those fragments are put together on the machine you're managing. You can even configure it such that local users on the system can add their own fragments that won't be removed by Puppet, if that's what works for you.
sshd_config { 'ListenAddress':
ensure => present,
value => $ipaddress_eth0
}
sshd_config { 'PermitRootLogin':
ensure => present,
value => 'no',
}
Finally, the pattern I'm most excited about. These Puppet resources are provided by the domcleal-augeasproviders Forge module. The foundation is the rock-solid Augeas file manipulation tool. It specializes in understanding every element of a configuration file which allows it to make very specific modifications without requiring the entire file to be managed. Purists may use the built-in augeas type but for the rest of us, the Forge module combines the simplicity of the Puppet DSL with the flexibility and power of Augeas.
It's so elegant that you can even ask Puppet to tell you about the state of every keyword in sshd_config in it's own language.
[root@rhel ~]# puppet resource sshd_config
sshd_config { 'ChallengeResponseAuthentication':
ensure => 'present',
value => ['no'],
}
sshd_config { 'ClientAliveInterval':
ensure => 'present',
value => ['420'],
}
sshd_config { 'GSSAPIAuthentication':
ensure => 'present',
value => ['yes'],
}
…
If you combine the sshd_config resources you want to manage with a special resource named resources, you can instruct Puppet to include only the things you've expressed in your managed machines sshd_config. Surgical precision or a nuke from orbit, it's your choice.
Try this stuff by installing Puppet or try Puppet Enterprise with everything ready to go for free on up to 10 machines. Learn much more about using Puppet at http://puppetlabs.com/learn.


2017-18 Committee Chairperson D Sai Pranav Reddy Vice Chair D Vishnu Priya Treasurer N Uthej Kumar Web Master V Abhinav


DOC HOLLYWOOD A film review by Frank Maloney Copyright 1991 Frank Maloney
DOC HOLLYWOOD is a movie directed by Michael Caton-Jones. The screenplay is by Jeffrey Price, Peter S. Seaman, and Daniel Pyne, based on the book "What? ... Dead Again?" by Neil B. Shulman, M.D. It stars Michael J. Fox, Julie Warner, David Odgen Stiers, Woody Harelson, and Bridget Fonda. Rated PG-13, for mature humor and brief nudity.
DOC HOLLYWOOD is being called by the local newspaper critics Southern Exposure; apparently the plot is virtually identical to the current hit TV series "Northern Exposure." You tell me, since I live in a TV-free zone (as I like to mention from time to time), but it does sound remarkably similar. A young, hot doc on his way to major bucks instead gets stranded in a looney-bin hick town. In Fox's case, the town is Grady, S.C., (admirably played by Micanopy, Fla.), a town apparently as TV-free as my own living room. The fantasy nature of DOC HOLLYWOOD is most evident in the lack of TV or radio or newspapers or anything else that might connect the loonies of Grady, "The Squash Capital of the South," "the buckle on the Bible Belt," with the outside world. Once Fox misses the freeway access, he and we are in a Twilight Zone episode, and if you find yourself looking for a pre-cancerous Rod Serling to smoulder out from behind a porch post saying "For your consideration," you are on the correct wavelength.
It's also a little hard to accept Fox as a hotshot, since the only reason we're given to accept his status as a major surgical talent is his show-room perfect 1956 Porsche. On the other hand, Fox is cute, effortlessly funny, energetic, and entertaining. (And I note with some pleasure that neither disease nor accident nor violence is necessary to change this snotty, heartless, little prick into a real mensch -- unlike THE DOCTOR or REGARDING HENRY.)
Other cast members are well chosen. Bridget Fonda is the mayor's daughter, who will do anything to get to L.A.; her performance has a kind of Fifties ambience to it -- sexy, innocent, open, devious -- and I find myself liking her a lot. The mayor is David Ogden Stiers, to whom the years since the end of M*A*S*H have not been particularly kind, but who is still capable of a kind of all-out, pedal-to-the-metal performance. Julie Warner is very attractive; the first we see of her is a skinny dipping scene that is probably more than a trifle gratuitous; it just doesn't make sense dramatically, but as an excuse for showcasing her beautiful breasts and nates I'm sure many of the audience felt it worked. Woody Harelson puts in an interesting performance as the insurance man who wants to sign up Warner for a life policy; he also gets off a major funny at the expense of Ted Danson, his co-star on "Cheers," as I understand it.
The movie also has a couple of amusing cameos: the director plays the maitre d'hotel in a Beverly Hills beanery and the head of the plastic-surgery that Fox wants a job at turns out to be an uncredited and entirely appropriate choice. This is not quite the secret as the ROBIN HOOD cameo, but I can stand not spoiling for you.
Caton-Jones, the director also of MEMPHIS BELLE, seems quite comfortable with his Southern locale, despite his own Scottish nationality. Unfortunately, the scriptwriters were less than original overall. They did manage to come up with a few scenes that really worked, such as the ultra-romantic scene of Fox and Warner dancing at the town squash festival, and the tone of the movie in general light, harmless, and it moves along at a fairly good clip. It's a little too long, a little too predictable, a little unmotivated here and there, but it still manages to provides some entertainment. And right now in the dog days of summer releases, that's a lot.
I recommend DOC HOLLYWOOD to a tolerant viewer who's looking for some late summer entertainment. But pay matinee prices, that's all it's worth, but it is worth that much.
-- Frank Richard Aloysius Jude Maloney .
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


{% extends 'base.html' %} {% load headers %} {% block page_title %}{{ title }} - {{ block.super }}{% endblock %} {% block page_content %} {% content_header title %}
A trade barrier is something that slows down or stops your company from exporting goods or services to an overseas market.
Report a trade barrier or an issue with an existing trade barrier on great.gov.uk.
If you need urgent help with a trade barrier, consider contacting your local British embassy, consulate or high commission their local knowledge may help to resolve your issue.
{% endblock %}


Total Revenue
$65,650
65% lower growth
Orders
3455
Product-wise sales
Sales
5693
Weekly Sales
Employees
246
Product-wise sales
Orders
| 오늘날짜너주셈 | 이름 | 연락처 | 발송예정일 | 발송장 |
|---|---|---|---|---|
| 1 | Herman Beck |
|
$ 77.99 | 53.64% |
| 2 | Messsy Adam |
|
$245.30 | 24.56% |
| 3 | John Richards |
|
$138.00 | 28.76% |
| 4 | Peter Meggik |
|
$ 77.99 | 53.45% |
| 5 | Edward |
|
$ 160.25 | 18.32% |
| 6 | Henry Tom |
|
$ 150.00 | 24.67% |


[ Back
Mode 7 Input:
To use this page: Simply select a sample file from the dropdown list. Or use 'Choose Files' below to load a local Teletext file of teletext data. You can also input or edit the text in this box, using backslashes and d or x to escape hex and decimal values: \x81 like\d131this! \xff\d255\xa3\d163 The Teletext formatted output is shown below, and the source for that output is in the box at the bottom of the page.
Columns
Rows
Double Height Echo
Binary:
Sample Binary...
Ascii Table
Channel 4 Logo
Central Logo
Colour Bars
Compufax Viewdata System
Default (instructions)
Edge Test
Election '97 Index
Election '97 Results
Engineering Testcard (Stardot)
Engineering Testcard (Alternate)
TV Guide
Frames:
Sample Frames...
Teletext40 2015-04-22
Keyboard Frustration
Jeff Running
Muybridge's Horse
Swirl
Seven Segment Display
Annoying Hampster
Annoying Banana
Page:
+
-
Sub:
+
-
/
1
Reveal
Play
ms
Source Output:
Teletext40 Output:
Teletext font by
<EMAIL_ADDRESS>2014
Home
Top
Static
Email


| Bits | Field | Descriptions |
| [0] | TMR_EN | Timer Counter Enable Control |
| | 0 = Stops/Suspends counting. |
| | 1 = Starts counting. |
| | Note1: Set TMR_EN to 1 enables 24-bit counter keeps up counting from the last stop counting value. |
| | Note2: This bit is auto-cleared by hardware in one-shot mode (MODE_SEL (TMRx_CTL[5:4]) = 00) once the value of 24-bit up counter equals the TMRx_CMPR. |
| [1] | SW_RST | Software Reset |
| | Set this bit will reset the timer counter, pre-scale counter and also force TMR_EN (TMRx_CTL [0]) to 0. |
| | 0 = No effect. |
| | 1 = Reset Timer's pre-scale counter, internal 24-bit up-counter and TMR_EN (TMRx_CTL [0]) bit. |
| | Note: This bit will be auto cleared and takes at least 3 TMRx_CLK clock cycles. |
| [2] | WAKE_EN | Wake-Up Enable Control |
| | When WAKE_EN is set and the TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) is set, the timer controller will generate a wake-up trigger event to CPU. |
| | 0 = Wake-up trigger event Disabled. |
| | 1 = Wake-up trigger event Enabled. |
| [3] | DBGACK_EN | ICE Debug Mode Acknowledge Ineffective Enable Control |
| | 0 = ICE debug mode acknowledgement effects TIMER counting and TIMER counter will be held while ICE debug mode acknowledged. |
| | 1 = ICE debug mode acknowledgement is ineffective and TIMER counter will keep going no matter ICE debug mode acknowledged or not. |
| [5:4] | MODE_SEL | Timer Operating Mode Select |
| | 00 = The timer is operating in the one-shot mode. |
| | In this mode, the associated interrupt signal is generated (if TMR_IER [TMR_IE] is enabled) once the value of 24-bit up counter equals the TMRx_CMPR. |
| | And TMR_CTL [TMR_EN] is automatically cleared by hardware. |
| | 01 = The timer is operating in the periodic mode. |
| | In this mode, the associated interrupt signal is generated periodically (if TMR_IER [TMR_IE] is enabled) while the value of 24-bit up counter equals the TMRx_CMPR. |
| | After that, the 24-bit counter will be reset and starts counting from zero again. |
| | 10 = The timer is operating in the periodic mode with output toggling. |
| | In this mode, the associated interrupt signal is generated periodically (if TMR_IER [TMR_IE] is enabled) while the value of 24-bit up counter equals the TMRx_CMPR. |
| | After that, the 24-bit counter will be reset and starts counting from zero again. |
| | At the same time, timer controller will also toggle the output pin TMRx_TOG_OUT to its inverse level (from low to high or from high to low). |
| | Note: The default level of TMRx_TOG_OUT after reset is low. |
| | 11 = The timer is operating in continuous counting mode. |
| | In this mode, the associated interrupt signal is generated when TMR_DR = TMR_CMPR (if TMR_IER [TMR_IE] is enabled). |
| | However, the 24-bit up-counter counts continuously without reset. |
| [6] | ACMP_EN_TMR | ACMP Trigger Timer Enable Control |
| | This bit high enables the functionality that when ACMP0 is in sigma-delta mode, it could enable Timer. |
| | 0 = ACMP0 trigger timer functionality disabled. |
| | 1 = ACMP0 trigger timer functionality enabled. |
| [7] | TMR_ACT | Timer Active Status Bit (Read Only) |
| | This bit indicates the timer counter status of timer. |
| | 0 = Timer is not active. |
| | 1 = Timer is in active. |
| [8] | ADC_TEEN | Timer Trigger ADC Enable Control |
| | This bit controls if TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) could trigger ADC. |
| | When ADC_TEEN is set, TMR_IS (TMRx_ISR[0]) is set and the CAP_TRG_EN (TMRx_CTL[11]) is low, the timer controller will generate an internal trigger event to ADC controller. |
| | When ADC_TEEN is set, TCAP_IS (TMRx_ISR[1]) is set and the CAP_TRG_EN (TMRx_CTL[11]) is high, the timer controller will generate an internal trigger event to ADC controller. |
| | 0 = TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) trigger ADC Disabled. |
| | 1 = TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) trigger ADC Enabled. |
| [10] | PDMA_TEEN | Timer Trigger PDMA Enable Control |
| | This bit controls if TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) could trigger PDMA. |
| | When PDMA_TEEN is set, TMR_IS (TMRx_ISR[0]) is set and the CAP_TRG_EN (TMRx_CTL[11]) is low, the timer controller will generate an internal trigger event to PDMA controller. |
| | When PDMA_TEEN is set, TCAP_IS (TMRx_ISR[1]) is set and the CAP_TRG_EN (TMRx_CTL[11]) is high, the timer controller will generate an internal trigger event to PDMA controller. |
| | 0 = TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) trigger PDMA Disabled. |
| | 1 = TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) trigger PDMA Enabled. |
| [11] | CAP_TRG_EN | TCAP_IS Trigger Mode Enable |
| | This bit controls if the TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) is used to trigger PDMA and ADC while TMR_IS (TMRx_ISR[0]) or TCAP_IS (TMRx_ISR[1]) is set. |
| | If this bit is low and TMR_IS (TMRx_ISR[0]) is set, timer will generate an internal trigger event to PDMA or ADC while related trigger enable bit (PDMA_TEEN (TMRx_CTL[10]) or ADC_TEEN (TMRx_CTL[8])) is set. |
| | If this bit is set high and TCAP_IS (TMRx_ISR[0]) is set, timer will generate an internal trigger event to PDMA or ADC while related trigger enable bit (PDMA_TEEN (TMRx_CTL[10]) or ADC_TEEN (TMRx_CTL[8])) is set. |
| | 0 = TMR_IS (TMRx_ISR[0]) is used to trigger PDMA and ADC. |
| | 1 = TCAP_IS (TMRx_ISR[1]) is used to trigger PDMA and ADC. |
| [12] | EVENT_EN | Event Counting Mode Enable Control |
| | When EVENT_EN is set, the increase of 24-bit up-counting timer is controlled by external event pin. |
| | While the transition of external event pin matches the definition of EVENT_EDGE (TMRx_CTL[13]), the 24-bit up-counting timer increases by 1. |
| | Or, the 24-bit up-counting timer will keep its value unchanged. |
| | 0 = Timer counting is not controlled by external event pin. |
| | 1 = Timer counting is controlled by external event pin. |
| [13] | EVENT_EDGE | Event Counting Mode Edge Selection |
| | This bit indicates which edge of external event pin enabling the timer to increase 1. |
| | 0 = A falling edge of external event enabling the timer to increase 1. |
| | 1 = A rising edge of external event enabling the timer to increase 1. |
| [14] | EVNT_DEB_EN | External Event De-Bounce Enable Control |
| | When EVNT_DEB_EN is set, the external event pin de-bounce circuit will be enabled to eliminate the bouncing of the signal. |
| | In de-bounce circuit the external event pin will be sampled 4 times by TMRx_CLK. |
| | 0 = De-bounce circuit Disabled. |
| | 1 = De-bounce circuit Enabled. |
| | Note: When EVENT_EN (TMRx_CTL[12]) is enabled, enable this bit is recommended. |
| | And, while EVENT_EN (TMRx_CTL[12]) is disabled, disable this bit is recommended to save power consumption. |
| [16] | TCAP_EN | TC Pin Functional Enable Control |
| | This bit controls if the transition on TC pin could be used as timer counter reset function or timer capture function. |
| | 0 = The transition on TC pin is ignored. |
| | 1 = The transition on TC pin will result in the capture or reset of 24-bit timer counter. |
| | Note: For TMRx_CTL, if INTR_TRG_EN (TMRx_CTL[24]) is set, the TCAP_EN will be forced to low and the TC pin transition is ignored (where x = 0 or 2). |
| | Note: For TMRx+1_CTL, if INTR_TRG_EN (TMRx_CTL[24]) is set, the TCAP_EN will be forced to high (where x = 0 or 2). |
| [17] | TCAP_MODE | TC Pin Function Mode Selection |
| | This bit indicates if the transition on TC pin is used as timer counter reset function or timer capture function. |
| | 0 = The transition on TC pin is used as timer capture function. |
| | 1 = The transition on TC pin is used as timer counter reset function. |
| | Note: For TMRx+1_CTL, if INTR_TRG_EN (TMRx_CTL[24]) is set, the TCAP_MODE will be forced to low (where x = 0 or 2). |
| [19:18] | TCAP_EDGE | TC Pin Edge Detect Selection |
| | This field defines that active transition of Tcapture pin is for timer counter reset function or for timer capture function. |
| | For timer counter reset function and free-counting mode of timer capture function, the configurations are: |
| | 00 = A falling edge (1 to 0 transition) on Tcapture pin is an active transition. |
| | 01 = A rising edge (0 to 1 transition) on Tcapture pin is an active transition. |
| | 10 = Both falling edge (1 to 0 transition) and rising edge (0 to 1 transition) on Tcapture pin are active transitions. |
| | 11 = Both falling edge (1 to 0 transition) and rising edge (0 to 1 transition) on Tcapture pin are active transitions. |
| | For trigger-counting mode of timer capture function, the configurations are: |
| | 00 = 1st falling edge on Tcapture pin triggers 24-bit timer to start counting, while 2nd falling edge triggers 24-bit timer to stop counting. |
| | 01 = 1st rising edge on Tcapture pin triggers 24-bit timer to start counting, while 2nd rising edge triggers 24-bit timer to stop counting. |
| | 10 = Falling edge on Tcapture pin triggers 24-bit timer to start counting, while rising edge triggers 24-bit timer to stop counting. |
| | 11 = Rising edge on Tcapture pin triggers 24-bit timer to start counting, while falling edge triggers 24-bit timer to stop counting. |
| | Note: For TMRx+1_CTL, if INTR_TRG_EN is set, the TCAP_EDGE will be forced to 11. |
| [20] | TCAP_CNT_MOD | Timer Capture Counting Mode Selection |
| | This bit indicates the behavior of 24-bit up-counting timer while TCAP_EN (TMRx_CTL[16]) is set to high. |
| | If this bit is 0, the free-counting mode, the behavior of 24-bit up-counting timer is defined by MODE_SEL (TMRx_CTL[5:4]) field. |
| | When TCAP_EN (TMRx_CTL[16]) is set, TCAP_MODE (TMRx_CTL[17]) is 0, and the transition of TC pin matches the TCAP_EDGE (TMRx_CTL[19:18]) setting, the value of 24-bit up-counting timer will be saved into register TMRx_TCAP. |
| | If this bit is 1, Trigger-counting mode, 24-bit up-counting timer will be not counting and keep its value at 0. |
| | When TCAP_EN (TMRx_CTL[16]) is set, TCAP_MODE (TMRx_CTL[17]) is 0, and once the transition of external pin matches the 1st transition of TCAP_EDGE (TMRx_CTL[19:18]) setting, the 24-bit up-counting timer will start counting. |
| | And then if the transition of external pin matches the 2nd transition of TCAP_EDGE (TMRx_CTL[19:18]) setting, the 24-bit up-counting timer will stop counting. |
| | And its value will be saved into register TMRx_TCAP. |
| | 0 = Capture with free-counting timer mode. |
| | 1 = Capture with trigger-counting timer mode. |
| | Note: For TMRx+1_CTL, if INTR_TRG_EN (TMRx_CTL[24]) is set, the TCAP_CNT_MOD will be forced to high, the capture with Trigger-counting Timer mode (where x = 0 or 2). |
| [22] | TCAP_DEB_EN | TC Pin De-Bounce Enable Control |
| | When CAP_DEB_EN (TMRx_CTL[22]) is set, the TC pin de-bounce circuit will be enabled to eliminate the bouncing of the signal. |
| | In de-bounce circuit the TC pin signal will be sampled 4 times by TMRx_CLK. |
| | 0 = De-bounce circuit Disabled. |
| | 1 = De-bounce circuit Enabled. |
| | Note: When TCAP_EN (TMRx_CTL[16]) is enabled, enable this bit is recommended. |
| | And, while TCAP_EN (TMRx_CTL[16]) is disabled, disable this bit is recommended to save power consumption. |
| | Note: When CAP_SRC (TMRx_ECTL[16]) is high, the capture signal is from internal of chip and the de-bounce circuit would not take effect no matter this bit is high or low. |
| | Note: For Timer 1 and 3, when INTR_TRG_EN (TMRx_CTL[24]) is high, the capture signal is from internal of chip and the de-bounce circuit would not take effect no matter this bit is high or low. |
| [24] | INTR_TRG_EN | Inter-Timer Trigger Function Enable Control |
| | This bit controls if Inter-timer Trigger function is enabled. |
| | If Inter-timer Trigger function is enabled, the TMRx will be in counter mode and counting with external Clock Source or event. |
| | In addition, TMRx+1 will be in trigger-counting mode of capture function. |
| | 0 = Inter-timer trigger function Disabled. |
| | 1 = Inter-timer trigger function Enabled. |
| | Note: For TMRx+1_CTL, this bit is ignored and the read back value is always 0. |
| [25] | INTR_TRG_MODE | Inter-Timer Trigger Mode Selection |
| | This bit controls the timer operation mode when inter-timer trigger function is enabled. |
| | When this bit is low, the TMRx will be in counter mode and counting with external Clock Source or event. |
| | In addition, TMRx+1 will be in trigger-counting mode of capture function. |
| | In this mode, TMRx_CMPR control when inter-timer trigger function terminated. |
| | When this bit is high, the TMRx will be in counter mode and counting with external Clock Source or event. |
| | In addition, TMRx+1 will be in trigger-counting mode of capture function. |
| | In this mode, TMRx+1_CMPR control when inter-timer trigger function terminated. |
| | In this mode, TMRx would ignore some incoming event based on the EVNT_DROP_CNT (TMRx_ECTL[31:24]). |
| | And once the TMRx+1 counter value equal or large than TMRx+1_CMPR, TMRx would terminate the operation when next incoming event received. |
| | 0 = Inter-Timer Trigger function wouldn't ignore any incoming event. |
| | 1 = Inter-Timer Trigger function would ignore incoming event based on the EVNT_DROP_CNT (TMRx_ECTL[31:24]). |
| | Note: For TMRx+1_CTL, this bit is ignored and the read back value is always 0. |


--- layout: demo title: Pointer events post-url: /2013/06/26/javascript-equivalents-in-css.html ---
In this demo you shouldn't be able to click the links. The js version is using event.preventDefault() and the css version is using pointer-events: none; You can read about pointer events more here.


CSS Pseudo Text and Screen Readers
View the full library of accessibility solutions.
The words bacon in the next paragraph is css pseudo content.
spicy jalapeno shankle jowl short loin, pig pork chop drumstick tri-tip porchetta
The following button's text is css pseudo content:


I need to Keep Synergy On Top Of All Running Applications
-
anonymous
It doesn't show when my Screen Saver is running.
-
Greg Hurrell
I'm not actively working on Synergy any more, but it's open source, so others are free to jump in and make changes if they want.
The level of the window is set here. I don't know whether one of the other window levels (currently listed here, but Apple likes shuffling their documentation around, so don't expect that link to work forever...) could be used to make the floater appear on top of the screensaver.
Reply
This topic is now closed.


{% load static %}
Tonify takes into account your thoughts and emotions through voice or text, generating a playlist based on your music choices.
Whether you're a student looking to showcase your work, a professional looking to attract clients, or a graphic artist looking to share your projects, this template is the perfect starting point!
Where to get started
Whether you're a student looking to showcase your work, a professional looking to attract clients, or a graphic artist looking to share your projects, this template is the perfect starting point!


Erros appear here
Werewolf is a multiplayer game where each player is assigned a role, and the village folk must identify the murderous werewolfs before it is too late! Read the full rules here.


Downlink – Technical structure
A simple way to share some links. Categories are available
Application model
Data tables
Link / Links
Basic settings
| Name |
Value |
Description |
| Leading |
|
Whether this represents the primary entity of the application |
| Display pattern |
#linkTitle# |
Pattern for displaying instances of this entity |
| ID strategy |
AUTO – Choose automatically. |
Whether and which identifier generation strategy is applied |
| Change tracking policy |
DEFERRED_IMPLICIT – Changes are determined by comparing properties during commit. |
How change detection is being done |
| Locking strategy |
PAGELOCK – Uses the PageLock module. |
Whether and which locking strategy is applied |
| Read only |
|
Whether this entity is read only or not. If yes, editing is not possible. |
Fields
| Name |
Type |
Mandatory |
Default value |
Display |
Constraints |
| Id |
Integer |
true |
|
ALL |
|
- This field is unique and allows no null values.
- Acts as primary key.
|
| Workflow state |
List |
true |
|
ALL |
- Has a length of 20 chars.
|
- the current workflow state
- This field is not unique and allows no null values.
- The list is represented by a single-valued dropdown list.
- Available entries:
- Initial (initial)
- Deferred (deferred)
- Approved (approved)
- Suspended (suspended)
- Trashed (trashed)
- Deleted (deleted)
|
| Link title |
String |
true |
|
ALL |
- Has a length of 255 chars.
|
- This field is not unique and allows no null values.
|
| My link |
URL |
true |
|
ALL |
- Has a length of 255 chars.
- The associated host is checked.
|
|
| My description |
Text |
false |
|
VIEW_DISPLAY |
- Has a length of 2000 chars.
|
|
Indexes
| Name |
Type |
Size |
Description |
| Workflow state index |
NORMAL – normal index |
1 field |
|
Actions
| Name |
Description |
| Index |
Index action in Link controller |
| View |
View action in Link controller |
| Display |
Display action in Link controller |
| Edit |
Edit action in Link controller |
| Delete |
Delete action in Link controller |
Workflow
| Name |
Description |
| Workflow type |
NONE – no approval. |
| States |
- Initial: content is just created and not persisted yet.
- Deferred: content has not been submitted yet or has been waiting, but was rejected. Allows users to manage their contributions, otherwise rejected content would be deleted.
- Approved: content has been approved and is available online.
- Suspended: content has been approved, but is temporarily offline.
- Deleted: content has been deleted from the database.
|
| Users are able to manage and edit their own data |
|
| If creator is deleted |
the "admin" user will be assigned. |
| If last editor is deleted |
the "admin" user will be assigned. |
Behaviour
| Name |
Value |
Name |
Value |
| Attributable |
|
Versionable |
|
| Categorisable |
|
Categories multi selection |
|
| Slugs |
|
|
|
| Tree |
NONE |
Geographical |
|
| Standard fields |
|
Hook subscribers |
|
| Form aware hooks provider |
DISABLED – no hook provider available |
UI hooks provider |
DISABLED – no hook provider available |
Configuration variables
List views
Here you can configure parameters for list views.
Sort value: 1
Composite:
Fields
| Name |
Type |
Mandatory |
Default value |
Display |
Constraints |
| Link entries per page |
Integer |
true |
10 |
ALL |
|
- The amount of links shown per page
- This field is not unique and allows no null values.
|
| Link own links on account page |
Boolean |
false |
true |
ALL |
|
- Whether to add a link to links of the current user on his account page
- This field is not unique and allows no null values.
|
Integration
These options allow you to configure integration aspects.
Sort value: 2
Composite:
Fields
| Name |
Type |
Mandatory |
Default value |
Display |
Constraints |
| Enabled finder types |
List |
false |
|
ALL |
- Has a length of 255 chars.
|
- Which sections are supported in the Finder component (used by Scribite plug-ins).
- This field is not unique and allows no null values.
- The list is represented by a multi-valued dropdown list
- Available entries:
|
Integration settings
| Setting |
Value |
Setting |
Value |
| System module |
|
Amount of example rows |
0 |
| Account panel |
|
Search integration |
|
| List view block |
|
Detail view block |
|
| List view content type |
|
Detail view content type |
|
| Mailz support |
|
Newsletter plugin |
|
| Moderation block |
|
Moderation panel |
|
| Pending content support |
|
MultiHook needles |
|
| External calls and Finder |
|
WYSIWYG plugins |
|
| Authentication method |
NONE – no authentication method available. |
Tagging support |
|
| Filter hooks provider |
DISABLED – no hook provider available |
Separate admin templates |
|
| RSS templates |
|
Atom templates |
|
| CSV templates |
|
XML templates |
|
| JSON templates |
|
KML templates |
|
| ICS templates |
|
PDF support |
|


June 30
But we see Jesus, who was made a little lower than the angels for the suffering of death, crowned with glory and honour; that he by the grace of God should taste death for every man. Hebrews 2:9
Death. It's not a popular topic--even among believers. In fact, a great many are just plain scared of it. Oh yes, they talk about having eternal life. Yet when the devil tries to threaten their earthly survival with sickness or calamity, they panic. Why? Because they haven't learned to look at death through God's eyes. Even though their spirit has been made immortal, they haven't renewed their minds to include that truth. If they had, when the devil tried to push their panic button, they'd just laugh and say, "You can't scare me, devil. I've done all the dying I'm ever going to do!"
That's true, you know. The Word of God says that you, as a born-again believer, are never going to see death (John 8:51). Jesus has been your substitute. He suffered death, so you wouldn't have to. And when He was raised, Hebrews 2:14-15 says, "He destroyed him that had the power of death, that is, the devil; And delivered them who through fear of death were all their lifetime subject to bondage."
 It occurred the instant you received Christ. At that moment, your old self--the one whose nature was to sin and rebel against God--died. Your body didn't die, but your spirit man--the real you-- died to Satan and all of his works. You became "a new creature" (2 Cor. 5:17), immortal and absolutely incapable of death!
When you're finished with your work on the earth, you're not going to die. You'll simply shed your earthly shell and relocate to a far more glorious place. Go to the Word and get God's perspective on death. Make a study of it. Once the reality of your immortality begins to dawn on you, the devil will never be able to threaten you with it again.
Scripture Reading: Hebrews 2:9-15


Comfort and Joy (1984)
Grade: 53
"Comfort and Joy" is a glacially paced whimsical comedy that doesn't quite make it. Bill Paterson stars as Alan Dickie, an Adult Contemporary disk jockey that is locally famous. Alan's live-in girlfriend, Maddy (Eleanor David), suddenly moves out leaving Alan distraught. His surgeon friend Colin (Patrick Malahide) is there to sympathize, but Alan finds himself fantasizing about Maddy and wistfully inspecting other women.
He sees a pretty woman in a "Mr. Bunny" ice cream truck. She smiles at him, and he follows the truck with his car. He is surprised to see goons wearing masks appear from nowhere and beat the truck with clubs. One of goons spots Alan and gets his autograph.
This incident has a strong impact on Alan. He becomes fascinated by ice cream, and makes an on-the-air offer to arbitrate the ice cream wars between "Mr. Bunny" and rival "Mr. McCool". He is so coy about this that his radio boss thinks he's lost it, sends Alan to a shrink, and takes him off the air. And Alan does seem to have lost, babbling on to everyone about ice cream and Mr. Bunny.
The only people who take Alan seriously are the feuding ice cream vendors. The McCool's are of Italian heritage, which apparently makes them act like mobsters, a stereotype complete with the head speaking Italian and the son translating and talking about family honor. Mr. Bunny has employed an attractive daughter of the McCool's. Worse, the Bunny's control the fish and chips market, that the McCool's want to break into.
Poor Alan is caught in the middle, naively attempting to arbitrate the dispute, and only ends up blamed by both sides and getting his beloved car bashed with clubs. But, eventually, Alan comes up with a solution. He invents a recipe for ice cream fritters and convinces Mr. Bunny and Mr. McCool to market the concoction as a "joint venture", taking a cut for himself as well. Apparently, Alan's boss is pleased as well, since Alan returns to the airwaves to plug his new product on his show as the credits roll.
Although "Comfort and Joy" is certainly watchable, it has its problems. The pace is too slow, and the various characters that are supposed to be humorous are not. The plot resolution is too tidy, as the warring clans band together upon one taste of Alan's recipe. The soundtrack is as tame and lame as Alan's on-air music. But perhaps the biggest mistake is the attempt to present violence and vandalism as something amusing.
http://members.tripod.com/~Brian_Koller/movies.html
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Tools for Happy Dungeons
Prestige Calculator
Prestige Calculator
Prestige Calculator
for
Happy Dungeons
Enter XP Earned and Time per Round to calculate amount of rounds and time to prestige.
XP
Minutes
Calculate
Results
Rounds to Prestige
Enter XP to see results
Time to Prestige
Enter Minutes to see results
XP Chart
XP from lv.1 - lv.50
Level
XP
Remaining XP
Rounds


Channel
resources that are not safely closed, including any instances created by calling
getChannel()
on a file or socket resource.
By default, the inspection assumes that the resources can be closed by any method with 'close' or 'cleanup' in its name.
Example:
void send(Socket socket) throws IOException {
SocketChannel channel = socket.getChannel(); //warning
channel.write(ByteBuffer.wrap("message".getBytes()));
}
Use the following options to configure the inspection:
Channel
resource is allowed to be opened inside a try
block.